| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Allow publishing partition changes via ancestors |
| Date: | 2020-04-09 13:07:03 |
| Message-ID: | CA+HiwqGmXKCMrW8DP5=KvkXqCddMpR0sVdrmUuchpaDe6b_YYA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On Thu, Apr 9, 2020 at 9:42 PM Andrew Dunstan
<andrew(dot)dunstan(at)2ndquadrant(dot)com> wrote:
> On 4/8/20 5:23 AM, Peter Eisentraut wrote:
> > Allow publishing partition changes via ancestors
> >
> > To control whether partition changes are replicated using their own
> > identity and schema or an ancestor's, add a new parameter that can be
> > set per publication named 'publish_via_partition_root'.
> >
> > This allows replicating a partitioned table into a different partition
> > structure on the subscriber.
>
> prion seems to be persistently unhappy with this. It uses
> -DRELCACHE_FORCE_RELEASE -DCATCACHE_FORCE_RELEASE, not sure if this
> could affect the result.
Patch to fix that has been posted on the -hackers thread:
https://www.postgresql.org/message-id/04d78603-edae-9243-9dde-fe3037176a7d%402ndquadrant.com
--
Amit Langote
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2020-04-09 13:39:36 | pgsql: Fix typo in pg_validatebackup documentation. |
| Previous Message | Andrew Dunstan | 2020-04-09 12:42:37 | Re: pgsql: Allow publishing partition changes via ancestors |