Thanks for the response, Tom. I think that's exactly what's going on here.
On Wed, Aug 3, 2022 at 11:28 AM Tom Lane wrote:
> Adrian Klaver writes:
> > On 8/3/22 08:09, Kevin Martin wrote:
> >> I thought that any UPDATE message in the replication logs is designed
> to
> >> include all values fo
Adrian Klaver writes:
> On 8/3/22 08:09, Kevin Martin wrote:
>> I thought that any UPDATE message in the replication logs is designed to
>> include all values for all columns. Is that correct?
Buried deep in the wire protocol specification is this bit:
The following message parts are shar
ed 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
hanks.
>
> -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
ed 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.kla...@aklaver.com
ve 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
