Re: Fix pg_publication_tables to exclude generated columns - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Fix pg_publication_tables to exclude generated columns
Date
Msg-id CAA4eK1+qienA1eSSSXZoxmFpx7bVkjVcCPhE_Ku9ymGvmhOwvg@mail.gmail.com
Whole thread Raw
In response to Fix pg_publication_tables to exclude generated columns  ("shiy.fnst@fujitsu.com" <shiy.fnst@fujitsu.com>)
Responses Re: Fix pg_publication_tables to exclude generated columns
List pgsql-hackers
On Mon, Jan 9, 2023 at 5:29 PM shiy.fnst@fujitsu.com
<shiy.fnst@fujitsu.com> wrote:
>
> I noticed that there is a problem about system view pg_publication_tables when
> looking into [1]. The column "attnames" contains generated columns when no
> column list is specified, but generated columns shouldn't be included because
> they are not replicated (see send_relation_and_attrs()).
>
> I think one way to fix it is to modify pg_publication_tables query to exclude
> generated columns. But in this way, we need to bump catalog version when fixing
> it in back-branch. Another way is to modify function
> pg_get_publication_tables()'s return value to contain all supported columns if
> no column list is specified, and we don't need to change system view.
>

That sounds like a reasonable approach to fix the issue.

-- 
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: XID formatting and SLRU refactorings (was: Add 64-bit XIDs into PostgreSQL 15)
Next
From: Andrew Dunstan
Date:
Subject: Re: Add support for DEFAULT specification in COPY FROM