From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_get_publication_tables() output duplicate relid |
Date: | 2021-11-22 07:24:45 |
Message-ID: | CA+HiwqHM2-+wUgiQRcMVU1NFCZ25dkED1kZm2T0PfcB+tb886A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Nov 19, 2021 at 2:28 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> On Fri, Nov 19, 2021 at 7:19 AM Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
> > As in,
> > do we know of any replication (initial/streaming) misbehavior caused
> > by the duplicate partition OIDs in this case or is the only problem
> > that pg_publication_tables output looks odd?
>
> The latter one but I think either we should document this or change it
> as we can't assume users will follow what subscriber-side code does.
On second thought, I agree that de-duplicating partitions from this
view is an improvement.
--
Amit Langote
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Andy Fan | 2021-11-22 07:43:23 | Re: Sequence's value can be rollback after a crashed recovery. |
Previous Message | Peter Eisentraut | 2021-11-22 07:23:08 | Re: dfmgr additional ABI version fields |