From: | Rahila Syed <rahilasyed90(at)gmail(dot)com> |
---|---|
To: | vignesh C <vignesh21(at)gmail(dot)com> |
Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Added schema level support for publication. |
Date: | 2021-01-20 12:57:47 |
Message-ID: | CAH2L28vd46csC=mbKdz24BRpr-XeFz8yLSY-sCy7xb_RYVQ32A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Vignesh,
> I have handled the above scenario(drop schema should automatically
> remove the schema entry from publication schema relation) & addition
> of tests in the new v2 patch attached.
> Thoughts?
>
Please see some initial comments:
1. I think there should be more tests to show that the schema data is
actually replicated
to the subscriber. Currently, I am not seeing the data being replicated
when I use FOR SCHEMA.
2. How does replication behave when a table is added or removed from a
subscribed schema
using ALTER TABLE SET SCHEMA?
3. Can we have a default schema like a public or current schema that gets
replicated in case the user didn't
specify one, this can be handy to replicate current schema tables.
4. + The fourth, fifth and sixth variants change which schemas are part
of the
+ publication. The <literal>SET TABLE</literal> clause will replace the
list
+ of schemas in the publication with the specified one. The <literal>ADD
There is a typo above s/SET TABLE/SET SCHEMA
Thank you,
Rahila Syed
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2021-01-20 13:28:34 | Re: [PATCH] postgres_fdw connection caching - cause remote sessions linger till the local session exit |
Previous Message | torikoshia | 2021-01-20 12:18:35 | Re: TOAST condition for column size |