| From: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | primary_conninfo and restore_command ? |
| Date: | 2022-03-10 13:51:16 |
| Message-ID: | CAKoxK+4b-FER9+AcOR0P7EC0KQQW9Am=TNMm5SnCE=j_nRW1yg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi all,
a friend of mine has shown to me a "strange" configuration of its
physical replication server (13): he has both primary_conninfo and
primary_slot_name, with replication slots active when queried on the
master. So far so good, but in the configuration he has also
restore_command to restore archived WALs from a centralized location.
Does this make sense?
Because if the replica cannot connect to the master, it will not start
at all (so I guess no restore_command will be executed). On the other
hand if the replica can connect to the primary the WALs will be
shipped by means of streaming.
Am I missing something?
Luca
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2022-03-10 14:04:46 | Re: primary_conninfo and restore_command ? |
| Previous Message | Ken Tanzer | 2022-03-10 08:30:46 | Re: Simple Query Doesn't Even with Data |