| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | 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 12:42:37 |
| Message-ID: | 6383fb03-1ad2-6c78-3030-348dc54fd67f@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2020-04-09 13:07:03 | Re: pgsql: Allow publishing partition changes via ancestors |
| Previous Message | Michael Paquier | 2020-04-09 06:52:26 | Re: pgsql: Implement waiting for given lsn at transaction start |