alexey.rassokhin/tet123
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

DBZ-5490 Document the case when message.key.columns is set and REPLICA IDENTITY of the tables is not FULL.

Browse Source 
It breaks tombstone events to have the proper key created because non-primary key columns will be null, and their values in the key will also be null.
This commit is contained in:
PlugaruT 2023-03-09 20:21:17 +02:00 committed by Jiri Pechanec
parent 77d9c88ac3
commit 6d32e22549
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
documentation/modules/ROOT/pages/connectors/postgresql.adoc
View File

@ -2926,6 +2926,9 @@ For the `purchaseorders` tables in any schema, the columns `pk3` and `pk4` serve
There is no limit to the number of columns that you use to create custom message keys.
However, it's best to use the minimum number that are required to specify a unique key.
Note that having this property set and `REPLICA IDENTITY` set to `DEFAULT` on the tables, will cause the tombstone events to not be created properly if the key columns are not part of the primary key of the table. +
Setting `REPLICA IDENTITY` to `FULL` is the only solution.
|[[postgresql-publication-autocreate-mode]]<<postgresql-publication-autocreate-mode, `+publication.autocreate.mode+`>>
|_all_tables_
|Applies only when streaming changes by using link:https://www.postgresql.org/docs/current/sql-createpublication.html[the `pgoutput` plug-in].