From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Telium Technical Support <support@telium.ca>
To: pgsql-admin@lists.postgresql.org
Subject: Re: PostgreSQL recovery file syntax, ver 8.4 vs ver 9.5
Date: Tue, 20 Feb 2018 16:44:29 -0500
Message-ID: <0f2b60dc-b095-d04c-c242-b79fdcacd32b@2ndquadrant.com> (raw)
In-Reply-To: <000301d3aa8b$a70c17c0$f5244740$@telium.ca>
References: <000301d3aa8b$a70c17c0$f5244740$@telium.ca>
On 2/20/18 15:44, Telium Technical Support wrote:
> In postgreSQL version 8.4 it seems that you can place the db server into
> warm standby mode with the following setting in recovery.conf
>
> restore_command = 'pg_standby archiveDir %f %p %r'
>
> In postgreSQL version 9.5 I see the same option, but I also see what
> appears to be an alternative syntax in recovery.conf:
>
> standby_mode = (boolean)
> trigger_file = (string)
>
> So is this new syntax an alternative to the old syntax (both are
> accepted by PGSQL)? Any benefit to the new syntax?
>
> Does the new syntax mean that I can use the restore_command setting as
> well (to use my own copy command)?
A lot has changed between 8.4 and 9.5. Hot standby, streaming
replication, replication slots, and so on. You can continue to use
pg_standby, but the new facilities are better in many ways.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, support@telium.ca, pgsql-admin@lists.postgresql.org
Subject: Re: PostgreSQL recovery file syntax, ver 8.4 vs ver 9.5
In-Reply-To: <0f2b60dc-b095-d04c-c242-b79fdcacd32b@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox