| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Shubham Khanna <khannashubham1197(at)gmail(dot)com>, Rajendra Kumar Dangwal <dangwalrajendra888(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, euler(at)eulerto(dot)com |
| Subject: | Re: Pgoutput not capturing the generated columns |
| Date: | 2024-05-22 11:40:27 |
| Message-ID: | c15027aa-c431-4857-bf78-ff888d2d875a@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08.05.24 09:13, Shubham Khanna wrote:
> The attached patch has the changes to support capturing generated
> column data using ‘pgoutput’ and’ test_decoding’ plugin. Now if the
> ‘include_generated_columns’ option is specified, the generated column
> information and generated column data also will be sent.
It might be worth keeping half an eye on the development of virtual
generated columns [0]. I think it won't be possible to include those
into the replication output stream.
I think having an option for including stored generated columns is in
general ok.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2024-05-22 11:42:40 | Re: State of pg_createsubscriber |
| Previous Message | Peter Eisentraut | 2024-05-22 11:32:03 | Re: tydedef extraction - back to the future |