Search Postgresql Archives

Re: "Missing" column in Postgres logical replication update message

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 8/3/22 06:50, Kevin Martin wrote:
We have a replication slot set up on a database in Postgres 12.8. For one of the tables, when a row is created, we see a series of records come through - an INSERT followed by a handful of UPDATEs. All of these messages in the WAL files show all columns, except for the last UPDATE message, which is missing one of the columns. (The column in question is a JSONB field, and the data is not overly large - less than 1000 chars.)  We think this is causing the data to come into our data lake (via Stitch) with that column as NULL.

See the messages where and/or how?

What is the UPDATE command that is being given on primary?

Is the data showing up in the replica table?


My understanding is that all INSERT and UPDATE messages written to the replication logs are supposed to include all columns. But I can't find a definitive answer on that.

So, my first question is: Is it normal / expected for UPDATE messages in the replication logs to exclude any columns in the table?

And, of course, if that is unexpected behavior, I'd love to hear any thoughts on what may cause it.

Thanks.

-Kevin


FYI.  I have this question posted also on StackOverflow: https://stackoverflow.com/questions/73222107/missing-column-in-postgres-logical-replication-update-message <https://stackoverflow.com/questions/73222107/missing-column-in-postgres-logical-replication-update-message>



--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux