primary_conninfo and restore_command ?

Поиск
Список
Период
Сортировка
От Luca Ferrari
Тема primary_conninfo and restore_command ?
Дата
Msg-id CAKoxK+4b-FER9+AcOR0P7EC0KQQW9Am=TNMm5SnCE=j_nRW1yg@mail.gmail.com
обсуждение исходный текст
Ответы Re: primary_conninfo and restore_command ?  (Julien Rouhaud <rjuju123@gmail.com>)
Re: primary_conninfo and restore_command ?  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Список 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



В списке pgsql-general по дате отправления:

Предыдущее
От: Ken Tanzer
Дата:
Сообщение: Re: Simple Query Doesn't Even with Data
Следующее
От: Julien Rouhaud
Дата:
Сообщение: Re: primary_conninfo and restore_command ?