Re: Dividing progress/debug information in pg_standby, and stat before copy
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dimitri Fontaine <dfontaine@hi-media.com>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, Magnus Hagander <magnus@hagander.net>, Greg Smith <greg@2ndquadrant.com>, Selena Deckelmann <selenamarie@gmail.com>, Josh Berkus <josh@agliodbs.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Simon Riggs <simon@2ndquadrant.com>
Date: 2010-01-26T14:40:00Z
Lists: pgsql-hackers
Dimitri Fontaine <dfontaine@hi-media.com> writes: > 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? pg_standby didn't address that detail, either. regards, tom lane