| From: | vignesh C <vignesh21(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Shubham Khanna <khannashubham1197(at)gmail(dot)com>, Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, Rajendra Kumar Dangwal <dangwalrajendra888(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, euler(at)eulerto(dot)com |
| Subject: | Re: Pgoutput not capturing the generated columns |
| Date: | 2024-06-20 07:21:57 |
| Message-ID: | CALDaNm3Ufg872XqgPvBVzXHvUVenu-8+Gz2dyEuKq3CN0UxfKw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 19 Jun 2024 at 21:43, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>
> On 19.06.24 13:22, Shubham Khanna wrote:
> > All the comments are handled.
> >
> > The attached Patch contains all the suggested changes.
>
> Please also take a look at the proposed patch for virtual generated
> columns [0] and consider how that would affect your patch. I think your
> feature can only replicate *stored* generated columns. So perhaps the
> documentation and terminology in your patch should reflect that.
This patch is unable to manage virtual generated columns because it
stores NULL values for them. Along with documentation the initial sync
command being generated also should be changed to sync data
exclusively for stored generated columns, omitting virtual ones. I
suggest treating these changes as a separate patch(0003) for future
merging or a separate commit, depending on the order of patch
acceptance.
Regards,
Vignesh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2024-06-20 07:29:45 | Re: Remove distprep |
| Previous Message | Andrey M. Borodin | 2024-06-20 07:17:44 | Re: datfrozenxid > relfrozenxid w/ crash before XLOG_HEAP_INPLACE |