On Thu, Oct 31, 2024 at 9:55 PM Ajin Cherian <itsa...@gmail.com> wrote:

> I ran some tests and verified that the patch works with previous versions
> of PG12 and PG17
> 1. Verified with publications with generated columns and without generated
> columns on patched code and subscriptions on PG12 and PG17
> Observations:
>     a. If publication is created with publish_generated_columns=true or
> with generated columns mentioned explicitly, then tablesync will not copy
> generated columns but post tablesync the generated columns are replicated
>     b. Column list override (publish_generated_columns=false) behaviour
>
> These seem expected.
>
>
Currently the documentation does not talk about this behaviour, I suggest
this be added similar to how such a behaviour was documented when the
original row-filter version was committed.
Suggestion:
"If a subscriber is a pre-18 version, the initial table synchronization
won't publish generated columns even if they are defined in the publisher."

regards,
Ajin Cherian
Fujitsu Australia

Reply via email to