From: "Telium Technical Support" <support@telium.ca>
To: <pgsql-admin@lists.postgresql.org>
References: <000301d3aa8b$a70c17c0$f5244740$@telium.ca>
 <0f2b60dc-b095-d04c-c242-b79fdcacd32b@2ndquadrant.com>
In-Reply-To: <0f2b60dc-b095-d04c-c242-b79fdcacd32b@2ndquadrant.com>
Subject: RE: PostgreSQL recovery file syntax, ver 8.4 vs ver 9.5
Date: Tue, 20 Feb 2018 16:57:32 -0500
Organization: Telium
Message-ID: <002001d3aa95$d25940b0$770bc210$@telium.ca>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQKqgp6QkSRzuyEE8uZR+KE3gBHW7gIg0Fy4oe8fmfA=
Content-Language: en-us
Precedence: bulk

I actually need the log shipping so I can decide whether or not I want =
the
standby to accept data from the master (In case of master corruption).  =
I
have clients on ver 8.4 and 9.5 so I'm trying to figure out if I can =
share
config settings between clients.

-----Original Message-----
From: Peter Eisentraut [mailto:peter.eisentraut@2ndquadrant.com]=20
Sent: Tuesday, February 20, 2018 4:44 PM
To: Telium Technical Support <support@telium.ca>;
pgsql-admin@lists.postgresql.org
Subject: Re: PostgreSQL recovery file syntax, ver 8.4 vs ver 9.5

On 2/20/18 15:44, Telium Technical Support wrote:
> In postgreSQL version 8.4 it seems that you can place the db server=20
> into warm standby mode with the following setting in recovery.conf
>=20
> =A0 =A0=A0restore_command =3D 'pg_standby archiveDir %f %p %r'
>=20
> In postgreSQL version 9.5 I see the same option, but I also see what=20
> appears to be an alternative syntax in recovery.conf:
>=20
> =A0=A0 standby_mode =3D (boolean)
> =A0 =A0trigger_file =3D (string)
>=20
> So is this new syntax an alternative to the old syntax (both are=20
> accepted by PGSQL)? Any benefit to the new syntax?
>=20
> 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.

--=20
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services