Subject: Re: PostgreSQL recovery file syntax, ver 8.4 vs ver 9.5
To: Telium Technical Support <support@telium.ca>,
 pgsql-admin@lists.postgresql.org
References: <000301d3aa8b$a70c17c0$f5244740$@telium.ca>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <0f2b60dc-b095-d04c-c242-b79fdcacd32b@2ndquadrant.com>
Date: Tue, 20 Feb 2018 16:44:29 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0)
 Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <000301d3aa8b$a70c17c0$f5244740$@telium.ca>
Content-Type: text/plain; charset=windows-1252
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Precedence: bulk

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