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

From Dimitri Fontaine
Subject Re: Dividing progress/debug information in pg_standby, and stat before copy
Date
Msg-id 87hbq988qe.fsf@hi-media-techno.com
Whole thread Raw
In response to Re: Dividing progress/debug information in pg_standby, and stat before copy  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses 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>)
List 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 by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Dividing progress/debug information in pg_standby, and stat before copy
Next
From: Michael Meskes
Date:
Subject: Re: ECPG patch 4.1, out-of-scope cursor support in native mode