From: | Alexander Kukushkin <cyberdemn(at)gmail(dot)com> |
---|---|
To: | Paul Förster <paul(dot)foerster(at)gmail(dot)com> |
Cc: | Ian Barwick <ian(dot)barwick(at)2ndquadrant(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Highly academic: local etcd & Patroni Cluster for testing on a single host |
Date: | 2020-02-26 08:19:24 |
Message-ID: | CAFh8B==q=WKSAu5ed=vz7UjxWkuh_5czY95Pe+BrBy2g0x1xTg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
On Wed, 26 Feb 2020 at 08:55, Paul Förster <paul(dot)foerster(at)gmail(dot)com> wrote:
> no, with Patroni, replicas are always initiated by Patroni. Patroni copies the whole PGDATA including everything (postgresql.conf, etc.) in it to the replica site. When launching Patroni for the first time, all you need is its yaml configuration file and an empty PGDATA. It then will copy the whole master's PGDATA as is, launch the replica database cluster and start replication.
That's not correct, Patroni will happily pick up the existing data directory.
> Even if Patroni uses pg_basebackup internally (which I assume it does), there is no way to pass parameters to it.
This is also not correct. One can specify arbitrarily parameters for
pg_basebackup in the Patroni config file:
postgresql:
basebackup:
tablespace-mapping: /foo=/bar
waldir: /my/waldir
Regards,
--
Alexander Kukushkin
From | Date | Subject | |
---|---|---|---|
Next Message | Ian Barwick | 2020-02-26 08:27:22 | Re: Highly academic: local etcd & Patroni Cluster for testing on a single host |
Previous Message | Paul Förster | 2020-02-26 07:55:29 | Re: Highly academic: local etcd & Patroni Cluster for testing on a single host |