Commit Graph

69 Commits (main)

Author SHA1 Message Date
Bradford D. Boyle 84f30f3f44 DBZ-8403 Fix PostgreSQL 17 compilation
When compiling against PG17 on Debian testing with gcc 14, building
fails because of incompatible-pointer-type error. This commit updates
the macros added in e1f8714 to handle the pointer types.
2024-11-13 10:07:02 +01:00
Jiri Pechanec e1f87147b7 DBZ-8275 Support PostgreSQL 17 API 2024-10-16 10:41:33 +02:00
Mohammed Imran e709f326cb fixed md violations and added syntax hightlighted codeblocks 2023-05-19 09:08:15 -04:00
Polina Bungina cd4171a030 DBZ-5370 Add PostgreSQL 15 compatibility code 2022-10-18 08:55:01 +02:00
Jiri Pechanec c9b00aa8c0 DBZ-3937 Read OID as unsigned integer 2021-08-30 14:42:49 +02:00
Jiri Pechanec 7a8c8b8f46 DBZ-2565 Process infinite timestamps 2020-10-01 09:53:09 +02:00
Jiri Pechanec e29a2580a5 DBZ-1052 DBZ-1746 Add unknown message type 2020-01-30 12:27:04 +01:00
Jiri Pechanec 870ecfa976 DBZ-1052 Emit tx BEGIN/END messages 2020-01-30 12:27:04 +01:00
Jiri Pechanec 01126bfa89 DBZ-1549 Remove PostGIS dependency 2019-11-15 07:57:33 +01:00
Jiri Pechanec 7f1c6fefc3 DBZ-1540 Update RPM spec to 0.10.0 2019-10-09 12:22:34 +02:00
Jiri Pechanec 54e2c45f11 DBZ-1498 Provide precise interval value 2019-10-09 12:13:28 +02:00
Gunnar Morling 3c910fff12 DB-1367 Sending marker for unchanged TOAST columns 2019-09-25 15:06:32 +02:00
Gunnar Morling 44cf35d4b5
Adding instructions for re-generating ProtoBuf code 2019-07-01 12:26:09 +02:00
Jiri Pechanec 0b536f372e DBZ-1272 Relax Postgres version requirements 2019-05-21 17:15:57 +02:00
Jiri Pechanec c1a5f51179 DBZ-1272 Spec file for RPM package 2019-05-21 17:15:57 +02:00
Jiri Pechanec c719d3fa6a DBZ-1144 Do not translate geometry point (PostGIS) to PG point
This code was effectivelly dead. It was used only when PostGIS geometry type was created inside the public schema and was responsible for translating of PostGIS point to PG point. When we introduced the full support for PostGIS types in Debezium the code was no longer used as PostGIS types are typically created in separate schema.
So now we support

* POINT type (postgres point)
* postgis GEOMETRY in arbitrary schema (including geometry point)
2019-04-02 15:56:16 +02:00
Jeremy Finzel 2a60a18ab1 Clarify build instructions 2019-01-17 20:24:21 +01:00
Alexander Kukushkin c5068d5b42 DBZ-955 Remove unused function and variable 2018-10-31 15:55:59 +01:00
Alexander Kukushkin 105344ac58 DBZ-955 Fix compilation agains postgres 11 2018-10-31 15:55:43 +01:00
Garrett T e2da727139 Allow a custom pg_config to be specified 2018-04-19 14:13:42 +02:00
Jiri Pechanec 0d4db2816b DBZ-351 Numeric is passed with unlimited precision 2018-02-21 18:04:30 +01:00
Jiri Pechanec d9477a5b99 DBZ-542 Set protobuf required version to at least 1.2 2018-01-15 09:22:11 +01:00
Duncan Sands 8baab62456 DBZ-496 The call to MemoryContextReset frees all allocated memory, which is both more
efficient and more reliable than individually freeing each allocated object.
2017-11-29 16:28:18 +01:00
Jiri Pechanec e375003c3b DBZ-486 Replication message provides info about optionality 2017-11-29 15:50:38 +01:00
Jiri Pechanec 2f3179ef4e DBZ-485 Replication message provides full type info 2017-11-29 15:50:38 +01:00
Danila Kiver 6c1723a179 DBZ-445 Made postGIS support optional. 2017-11-15 08:27:26 +01:00
Randall Hauch d08a75593c Merge pull request #7 from DuncanSands/master
DBZ-277 Don't send per-row SQL warning messages to clients
2017-06-02 15:39:29 -05:00
Duncan Sands e248eda6a1 Don't use the WARNING log level for situations that can occur perfectly normally,
as WARNING messages are transmitted all the way to the client (i.e. are costly).
In my case I have lots of tables with types that aren't yet understood by
decoderbufs.  These tables aren't being monitored, but because logical decoding
works on the level of the entire database, not just the tables monitored, rows
from them are still reaching decoderbufs, generating vast numbers of warnings
  "Encountered unknown typid..."
Likewise, I have many unmonitored materialized views.  Every row deleted when
doing a concurrent refresh generates the warning
  "...no PK is present..."
These warnings cause two types of trouble when they hit the debezium postgres
connector: a memory leak and increased CPU usage.  The memory leak is because
the JDBC layer carefully preserves these warnings in a list, and the list is
never being cleared (this should be fixed in the connector).  As for the CPU
usage, I don't fully understand why the processing time increases so much.
It's normal that it should double, as there are twice as many packets to
process (one warning for every row), but it seems to take way more than twice
as long.
2017-06-02 21:56:12 +02:00
Randall Hauch 8a6a8305c3 Merge pull request #6 from nacivida/DBZ-223
DBZ-223 Handles dropped columns correctly.
2017-05-19 06:36:49 -05:00
Naci Ishakbeyoglu dbfe1fbbd5 DBZ-223 Handles dropped columns correctly. 2017-05-04 23:29:18 -07:00
Randall Hauch d9415fc78f Merge pull request #5 from CyberDem0n/master
Fix compilation warnings
2017-04-17 09:38:55 -05:00
Alexander Kukushkin fbb712f731 Fix compilation warnings 2017-04-11 15:21:08 +02:00
Randall Hauch 04f1dc3c9e Merge pull request #4 from hchiorean/DBZ-3
DBZ-3 Changes the output of the plugin to include the FQN of the table and fixes various plugin issues
2016-11-14 07:54:20 -06:00
Horia Chiorean 69ff80aee0 DBZ-3 Changes the output of the plugin to include the FQN of the table and fixes plugin issues regarding dropped columns 2016-11-10 10:14:31 +02:00
Randall Hauch 1baad6ecc6 Merge pull request #3 from hchiorean/DBZ-3
DBZ-3 Adds support for the CASH, BIT, JSONB, VARBIT, DATE,TIME,TIMETZ and INTERVAL oids
2016-11-04 09:28:52 -05:00
Horia Chiorean 6df63f806a DBZ-3 Adds support for the CASH, BIT, JSONB, VARBIT, DATE,TIME,TIMETZ and INTERVAL oids
It also changes the previous behavior for TIMESTAMP and TIMESTAMPTZ to return UTC style LONGs as opposed to STRINGS.
2016-11-04 16:06:03 +02:00
Horia Chiorean f921f2af59 Updates README and protobuf descriptor 2016-09-27 09:02:57 -05:00
Xavier 77afd40d7c Adding last name to license 2016-08-09 08:48:51 -07:00
Xavier ef6910f192 Update README.md 2015-07-31 16:27:37 -07:00
Xavier Stevens 610ea41409 Cleaned up debug print functions 2015-04-28 12:46:18 -07:00
Xavier Stevens 913b176e5d Sync'ing up branch 2015-04-28 10:23:14 -07:00
Xavier Stevens 6fe0d68393 Fixing bug after merging oneof use in protobuf definition 2015-04-27 15:18:45 -07:00
Xavier ba4a480643 Merge pull request #2 from jarreds/master
Use `oneof` for different datum field types
2015-04-20 20:36:11 -07:00
Jarred Ward 27db93ceb8 Use `oneof` for different datum field types 2015-04-20 16:34:00 -07:00
Xavier Stevens 29a7ac49dc Fixed protocol buffer error caused by not initializing properly 2015-02-11 12:40:08 -08:00
Xavier Stevens 5b7a88438e Fixing type lookups for PostGIS types, some memory allocation, etc. 2015-02-11 11:48:42 -08:00
Xavier Stevens 744b29fa7d Syncing up code so others can see latest 2015-02-10 10:30:39 -08:00
Xavier Stevens becb332b8c Switching fprintf usage to elog 2015-02-09 14:02:13 -08:00
Xavier Stevens e19e93e715 Fixing bug that snuck in around lwgeom checks 2015-01-20 15:34:55 -08:00
Xavier Stevens 2382a1d8d1 Merge branch 'master' of github.com:xstevens/decoderbufs 2015-01-20 15:24:00 -08:00