From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | "shiy(dot)fnst(at)fujitsu(dot)com" <shiy(dot)fnst(at)fujitsu(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Fix pg_publication_tables to exclude generated columns |
Date: | 2023-01-09 13:32:15 |
Message-ID: | CAA4eK1+qienA1eSSSXZoxmFpx7bVkjVcCPhE_Ku9ymGvmhOwvg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jan 9, 2023 at 5:29 PM shiy(dot)fnst(at)fujitsu(dot)com
<shiy(dot)fnst(at)fujitsu(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2023-01-09 13:52:41 | Re: Add support for DEFAULT specification in COPY FROM |
Previous Message | Aleksander Alekseev | 2023-01-09 13:30:47 | Re: XID formatting and SLRU refactorings (was: Add 64-bit XIDs into PostgreSQL 15) |