Hi Ian,
> On 26. Feb, 2020, at 09:27, Ian Barwick wrote:
> It doesn't - it takes the tablespace location directly from the symlink in
> the "pg_tblspc"
> directory (since PostgreSQL 9.2), so you can manipulate those manually,
> provided the server
> isn't running of course.
>
> Not sure how th
Hi Alexander,
> On 26. Feb, 2020, at 09:19, Alexander Kukushkin 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 t
On 2020/02/26 16:55, Paul Förster wrote:
Hi Ian,
On 26. Feb, 2020, at 01:38, Ian Barwick wrote:
Assuming the standby/replica is created using pg_basebackup, you can use the
-T/--tablespace-mapping option to remap the tablespace directories.
no, with Patroni, replicas are always initiated by
Hi,
On Wed, 26 Feb 2020 at 08:55, Paul Förster 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
Hi Ian,
> On 26. Feb, 2020, at 01:38, Ian Barwick wrote:
>
> Assuming the standby/replica is created using pg_basebackup, you can use the
> -T/--tablespace-mapping option to remap the tablespace directories.
no, with Patroni, replicas are always initiated by Patroni. Patroni copies the
whole P
On 2020/02/26 0:41, Paul Förster wrote:
Hi,
I have set up an etcd & Patroni cluster on a single machine for testing
purposes as follows:
/data/pg01a/db as data directory for the first "node"
/data/pg01b/db as data directory for the second "node"
I have set up Patroni to make each PostgreSQL d
