From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | Rafia Sabih <rafia(dot)pghackers(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: adding partitioned tables to publications |
Date: | 2020-01-29 07:29:55 |
Message-ID: | CA+HiwqGt89L5Sx5Mf2upYGsjw-pge7PdgYHQe3d6BnAcmevZ+w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jan 28, 2020 at 6:11 PM Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> This structure looks good now.
Thanks for taking a look.
> However, it does seem unfortunate that in pg_get_publication_tables() we
> need to postprocess the result of GetPublicationRelations(). Since
> we're already changing the API of GetPublicationRelations(), couldn't we
> also make it optionally not include partitioned tables?
Hmm, okay. We really need GetPublicationRelations() to handle
partitioned tables in 3 ways:
1. Don't expand and return them as-is
2. Expand and return only leaf partitions
3. Expand and return all partitions
I will try that in the new patch.
> For the test, perhaps add test cases where partitions are attached and
> detached so that we can see whether their publication relcache
> information is properly updated. (I'm not doubting that it works, but
> it would be good to have a test for, in case of future restructuring.)
Okay, I will add some to publication.sql.
Will send updated patches after addressing Rafia's comments.
Thanks,
Amit
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2020-01-29 08:10:20 | Re: Physical replication slot advance is not persistent |
Previous Message | Fabien COELHO | 2020-01-29 07:25:08 | Re: Add %x to PROMPT1 and PROMPT2 |