Re: pgsql: Allow publishing partition changes via ancestors - Mailing list pgsql-committers

From Amit Langote
Subject Re: pgsql: Allow publishing partition changes via ancestors
Date
Msg-id CA+HiwqGmXKCMrW8DP5=KvkXqCddMpR0sVdrmUuchpaDe6b_YYA@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Allow publishing partition changes via ancestors  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
List pgsql-committers
On Thu, Apr 9, 2020 at 9:42 PM Andrew Dunstan
<andrew.dunstan@2ndquadrant.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



pgsql-committers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: pgsql: Allow publishing partition changes via ancestors
Next
From: Fujii Masao
Date:
Subject: pgsql: Fix typo in pg_validatebackup documentation.