Re: Pgoutput not capturing the generated columns

From: Peter Smith <smithpb2250(at)gmail(dot)com>
To: vignesh C <vignesh21(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, "Shinoda, Noriyoshi (SXD Japan FSIP)" <noriyoshi(dot)shinoda(at)hpe(dot)com>, Shubham Khanna <khannashubham1197(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Rajendra Kumar Dangwal <dangwalrajendra888(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "euler(at)eulerto(dot)com" <euler(at)eulerto(dot)com>
Subject: Re: Pgoutput not capturing the generated columns
Date: 2025-01-20 03:29:06
Message-ID: CAHut+PspFmQJEGUXbH2KAfX+rfd7k0u-tT4Q=dA=vPKQzm8Log@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

IIUC, patch v53-0004 is primarily a bug fix for a docs omission of the
master implementation.

So,

1. IMO think this patch in its current form must come *before* the
0003 patch where you changed the PUBLICATION option from bool to enum.

2. Then the patch (currently called) 0003 needs to update this doc
fragment to change the type from bool to char; it should also itemise
the possible values 'n', 's' saying what those values mean.

======
Kind Regards,
Peter Smith.
Fujitsu Australia

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2025-01-20 03:52:48 Re: Skip collecting decoded changes of already-aborted transactions
Previous Message Sami Imseih 2025-01-20 03:27:57 Re: improve DEBUG1 logging of parallel workers for CREATE INDEX?