4e67dca3f1
Clarify build instructions
2019-01-17 12:31:41 -06:00
c5068d5b42
DBZ-955 Remove unused function and variable
2018-10-31 15:55:59 +01:00
105344ac58
DBZ-955 Fix compilation agains postgres 11
2018-10-31 15:55:43 +01:00
e2da727139
Allow a custom pg_config to be specified
2018-04-19 14:13:42 +02:00
0d4db2816b
DBZ-351 Numeric is passed with unlimited precision
2018-02-21 18:04:30 +01:00
d9477a5b99
DBZ-542 Set protobuf required version to at least 1.2
2018-01-15 09:22:11 +01:00
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
e375003c3b
DBZ-486 Replication message provides info about optionality
2017-11-29 15:50:38 +01:00
2f3179ef4e
DBZ-485 Replication message provides full type info
2017-11-29 15:50:38 +01:00
6c1723a179
DBZ-445 Made postGIS support optional.
2017-11-15 08:27:26 +01:00
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
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
8a6a8305c3
Merge pull request #6 from nacivida/DBZ-223
...
DBZ-223 Handles dropped columns correctly.
2017-05-19 06:36:49 -05:00
dbfe1fbbd5
DBZ-223 Handles dropped columns correctly.
2017-05-04 23:29:18 -07:00
d9415fc78f
Merge pull request #5 from CyberDem0n/master
...
Fix compilation warnings
2017-04-17 09:38:55 -05:00
fbb712f731
Fix compilation warnings
2017-04-11 15:21:08 +02:00
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
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
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
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
f921f2af59
Updates README and protobuf descriptor
2016-09-27 09:02:57 -05:00
77afd40d7c
Adding last name to license
2016-08-09 08:48:51 -07:00
ef6910f192
Update README.md
2015-07-31 16:27:37 -07:00
610ea41409
Cleaned up debug print functions
2015-04-28 12:46:18 -07:00
913b176e5d
Sync'ing up branch
2015-04-28 10:23:14 -07:00
6fe0d68393
Fixing bug after merging oneof use in protobuf definition
2015-04-27 15:18:45 -07:00
ba4a480643
Merge pull request #2 from jarreds/master
...
Use `oneof` for different datum field types
2015-04-20 20:36:11 -07:00
27db93ceb8
Use `oneof` for different datum field types
2015-04-20 16:34:00 -07:00
29a7ac49dc
Fixed protocol buffer error caused by not initializing properly
2015-02-11 12:40:08 -08:00
5b7a88438e
Fixing type lookups for PostGIS types, some memory allocation, etc.
2015-02-11 11:48:42 -08:00
744b29fa7d
Syncing up code so others can see latest
2015-02-10 10:30:39 -08:00
becb332b8c
Switching fprintf usage to elog
2015-02-09 14:02:13 -08:00
e19e93e715
Fixing bug that snuck in around lwgeom checks
2015-01-20 15:34:55 -08:00
2382a1d8d1
Merge branch 'master' of github.com:xstevens/decoderbufs
2015-01-20 15:24:00 -08:00
5594ad04ef
Fixing styling using clang-format
2015-01-20 15:23:45 -08:00
9d306851ab
Update README.md
2015-01-20 15:12:00 -08:00
b211211fdf
Adding support for Postgres Point as well as PostGIS Geometry/Geography Points
2015-01-20 15:09:29 -08:00
5d4368bbca
Changed output table to only use table name and exclude the schema
2015-01-16 14:43:34 -08:00
ec818d7d58
Merge branch 'master' of github.com:xstevens/decoderbufs
2015-01-07 10:59:34 -08:00
d3e1a15aad
Adding UUIDOID support
2015-01-07 10:32:14 -08:00
fddd4881dd
Update README.md
2014-10-16 14:53:59 -07:00
08803b8c92
Merge pull request #1 from stevensurgnier/master
...
clean up
2014-10-16 14:53:15 -07:00
7b7cd4e43a
4 space tabs
2014-10-16 21:42:11 +00:00
61afd1f768
decoder typo
2014-10-16 21:42:05 +00:00
cc0b8d56cb
Update README.md
2014-09-30 12:25:41 -07:00
37901c824e
Update README.md
2014-09-30 12:16:43 -07:00
aebc1ba672
Updating README
2014-09-30 12:09:45 -07:00
4f29f5c47f
Adding frame encoding and fixing handling of some types
2014-09-30 11:35:07 -07:00
be9ef38f1d
Adding timestamp oid support
2014-09-23 12:19:29 -07:00
f9d69b3f1f
Using clang-format to style nazi myself
2014-09-22 16:26:50 -07:00
Jeremy Finzel
Alexander Kukushkin
Garrett T
Jiri Pechanec
Duncan Sands
Danila Kiver
Randall Hauch
Naci Ishakbeyoglu
Horia Chiorean
Xavier
Xavier Stevens
Jarred Ward
Steven Surgnier