From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Telium Technical Support <support(at)telium(dot)ca>, pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: PostgreSQL recovery file syntax, ver 8.4 vs ver 9.5 |
Date: | 2018-02-20 21:44:29 |
Message-ID: | 0f2b60dc-b095-d04c-c242-b79fdcacd32b@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Telium Technical Support | 2018-02-20 21:57:32 | RE: PostgreSQL recovery file syntax, ver 8.4 vs ver 9.5 |
Previous Message | Telium Technical Support | 2018-02-20 20:44:44 | PostgreSQL recovery file syntax, ver 8.4 vs ver 9.5 |