Re: Hot standby problems: consistent state not reached, no connection to master server.

On 04/13/2015 01:05 PM, Guillaume Lelarge wrote:
> Le 12 avr. 2015 16:50, "Ilya Ashchepkov" <koctep@gmail.com
> <mailto:koctep@gmail.com>> a écrit :
>  >

>  > restore_command = '/usr/lib/postgresql/9.3/bin/pg_standby -t
> /tmp/pgsql.trigger.5432 /media/psqlbak/101/wals/main/ %f %p %r'
>  >
>
> Don't use pg_standby if you want to use streaming. Use cp, scp, rsync,
> or anything else but not pg_standby. Streaming starts when archive
> recovery fails to get next archive.
>

I have not used pg_standby, so the above was helpful. I now see that
warning in the docs:

http://www.postgresql.org/docs/9.3/static/warm-standby.html

25.2.4. Setting Up a Standby Server

"Note: Do not use pg_standby or similar tools with the built-in standby
mode described here. restore_command should return immediately if the
file does not exist; the server will retry the command again if
necessary. See Section 25.4 for using tools like pg_standby."

Going to section 25.4 explained a lot. Thanks for the information.



--
Adrian Klaver
adrian.klaver@aklaver.com