From: | KK CHN <kkchn(dot)in(at)gmail(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | WAL replication standby server: query |
Date: | 2024-10-15 17:10:53 |
Message-ID: | CAKgGyB-Mm6dorL2bFJA-9ZG04C99X+T-nQuYis9T0TU0OVSx0A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
List ,
I am trying to configure a WAL replicated standby server(EDB16) .. In
the archive command I used a dedicated "/data/archive " directory for
WAL archiving as follows, as I don't want any WAL overwriting in the
default WAL directory and loss of WAL files.
I have
archive_command= ' cp %p /data/archive/%f '
pg_hba.conf I have
host replication all 10.255.10.0/24 md5
My doubt is whether the standby Postgres server(EDB16) reads WAL files by
itself from the primary server's explicit WAL archive folder
/data/archive by its own ?
OR
The standby can read only from the default WAL location ie; pg_wal
directory of primary server ?
Please enlighten me.
If the standby can read only the default pg_wal folder, then how can we
make the standby server to read from the explicit " /data/archive "
folder for WAL syncing automatically to the standby ?
Any input is much appreciated.
Thank you,
Krishane
From | Date | Subject | |
---|---|---|---|
Next Message | Christophe Pettus | 2024-10-15 17:56:25 | Re: Advice on efficiently logging outputs to PostgreSQL |
Previous Message | Dominique Devienne | 2024-10-15 14:17:04 | Advice on efficiently logging outputs to PostgreSQL |