Re: Dividing progress/debug information in pg_standby, and stat before copy

Поиск
Список
Период
Сортировка
От Dimitri Fontaine
Тема Re: Dividing progress/debug information in pg_standby, and stat before copy
Дата
Msg-id 87hbq988qe.fsf@hi-media-techno.com
обсуждение исходный текст
Ответ на Re: Dividing progress/debug information in pg_standby, and stat before copy  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Ответы Re: Dividing progress/debug information in pg_standby, and stat before copy  (tomas@tuxteam.de)
Re: Dividing progress/debug information in pg_standby, and stat before copy  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Re: Dividing progress/debug information in pg_standby, and stat before copy  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> *That* makes pg_standby obsolete, not streaming replication per se.
> Setting standby_mode=on, with a valid restore_command using e.g 'cp' and
> no connection info for walreceiver is more or less the same as using
> pg_standby.

I've yet to understand how the files in the archive get from the master
to the slave in this case, or are you supposing in your example that the
cp in the restore_command is targetting a shared disk setup or
something?

Regards,
-- 
dim


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

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: Re: Dividing progress/debug information in pg_standby, and stat before copy
Следующее
От: Michael Meskes
Дата:
Сообщение: Re: ECPG patch 4.1, out-of-scope cursor support in native mode