Re: Dividing progress/debug information in pg_standby, and stat before copy - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Dividing progress/debug information in pg_standby, and stat before copy
Date
Msg-id 4B5EC5C6.1000103@enterprisedb.com
Whole thread Raw
In response to Re: Dividing progress/debug information in pg_standby, and stat before copy  (Dimitri Fontaine <dfontaine@hi-media.com>)
Responses Re: Dividing progress/debug information in pg_standby, and stat before copy  (Dimitri Fontaine <dfontaine@hi-media.com>)
List pgsql-hackers
Dimitri Fontaine wrote:
> 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?

Yes. Just like with pg_standby.

--  Heikki Linnakangas EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: tomas@tuxteam.de
Date:
Subject: Re: Dividing progress/debug information in pg_standby, and stat before copy
Next
From: Dimitri Fontaine
Date:
Subject: Re: Dividing progress/debug information in pg_standby, and stat before copy