| From: | Paul Förster <paul(dot)foerster(at)gmail(dot)com> |
|---|---|
| To: | Alexander Kukushkin <cyberdemn(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:40:21 |
| Message-ID: | 288541E6-FF55-4691-ABD0-1ED386E47DDD@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Alexander,
> On 26. Feb, 2020, at 09:19, Alexander Kukushkin <cyberdemn(at)gmail(dot)com> wrote:
> That's not correct, Patroni will happily pick up the existing data directory.
maybe I didn't express myself correctly. Of course it does. Otherwise replication wouldn't make sense. I meant, starting a Patroni replica for the first time will copy everything over from the master as it is.
> 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
I didn't know that. Thanks very much. :-) I'll give it a try.
So, this is a Patroni question and not a PostgreSQL question after all and actually doesn't belong here anyway. Still, thanks for the answer.
Cheers,
Paul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sándor Daku | 2020-02-26 09:22:12 | Re: Invoice increment |
| Previous Message | Søren Frisk | 2020-02-26 08:38:57 | Invoice increment |