From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_get_publication_tables() output duplicate relid |
Date: | 2021-11-24 06:32:04 |
Message-ID: | CA+HiwqHX8LzgDfWM4-ZKzNFgQxMqnfUBRa4YghQkJDtoW6Ou7Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Nov 23, 2021 at 12:21 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> Isn't it better to document this case and explain what
> users can expect instead of trying to design a solution around this?
I thought about the problems you've described and it looks like I
hadn't considered many of the details which complicate implementing a
solution for this.
So yeah, documenting the ATTACH issue as a limitation sounds like the
best course for now. I might word it as follows and add it under
Notes at https://www.postgresql.org/docs/current/sql-createpublication.html:
"ATTACHing a table into a partition tree whose root is published using
a publication with publish_via_partition_root set to true does not
result in the table's existing contents to be replicated."
I'm not sure there's a clean enough workaround to this that we can add
to the paragraph.
Does that make sense?
> Even if we do so the streaming after attach partition problem as
> discussed above should be fixed.
I agree. I have reproduced the problem though haven't managed to pin
down the cause yet.
--
Amit Langote
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2021-11-24 06:45:45 | Re: parallel vacuum comments |
Previous Message | Masahiko Sawada | 2021-11-24 06:18:59 | Re: parallel vacuum comments |