Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eoEnz-0003qy-IG for pgsql-admin@arkaria.postgresql.org; Tue, 20 Feb 2018 20:46:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eoEny-0000OL-9w for pgsql-admin@arkaria.postgresql.org; Tue, 20 Feb 2018 20:46:26 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eoEnx-0000OC-Pp for pgsql-admin@lists.postgresql.org; Tue, 20 Feb 2018 20:46:26 +0000 Received: from a2nlsmtp01-02.prod.iad2.secureserver.net ([198.71.225.36]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eoEnt-00072s-PH for pgsql-admin@lists.postgresql.org; Tue, 20 Feb 2018 20:46:25 +0000 Received: from a2plcpnl0131.prod.iad2.secureserver.net ([198.71.226.50]) by : HOSTING RELAY : with SMTP id oEmYeNq5qQvTSoEmYe8ZpS; Tue, 20 Feb 2018 13:44:58 -0700 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=telium.ca; s=default; h=Content-Type:MIME-Version:Message-ID:Date:Subject:To:From: Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=iFzN92AmRpouqptl+oN7TMK+rCTzubmLrmmj3dNUTIU=; b=L/FgUi/SwTXbQ1obgL1SA0qmnf xztG+jbgDFWcHO2HueGelTZq9oi94oUEH3st1cFFlYHqiVoaNxXiYqD9Murq/H34vFCp7TwvsC5MR Z2tCAlsHFvORTL2krXyj8SRR5dmgCH8zh6WiIjr8zdxwdo052UJYNUasLF+L0KKnMJU619LgrSv0G E1wLSa2b0qvEK6AciOqPIClFCkmzzmcVTj7STDf4/2ojVUXmXKboxrHMz5e4gR4B3HP7EIn32rCtk HhTTBD6K5WLkt8UJlUyAmQ+CqyF4w2L0OsGLvdt8v61lNVRY8sZkt1nxYDp7zxOhET4Y9CjAZdWDK jHkGbHfw==; Received: from [173.239.164.42] (port=57040 helo=vmltms) by a2plcpnl0131.prod.iad2.secureserver.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1eoEmY-003aen-BS for pgsql-admin@lists.postgresql.org; Tue, 20 Feb 2018 13:44:58 -0700 From: "Telium Technical Support" To: Subject: PostgreSQL recovery file syntax, ver 8.4 vs ver 9.5 Date: Tue, 20 Feb 2018 15:44:44 -0500 Organization: Telium Message-ID: <000301d3aa8b$a70c17c0$f5244740$@telium.ca> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01D3AA61.BE36AC00" X-Mailer: Microsoft Outlook 15.0 Thread-Index: AdOqg7GXv19elk7VQIGQYWBXwnydUw== Content-Language: en-us X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - a2plcpnl0131.prod.iad2.secureserver.net X-AntiAbuse: Original Domain - lists.postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - telium.ca X-Get-Message-Sender-Via: a2plcpnl0131.prod.iad2.secureserver.net: authenticated_id: support@telium.ca X-Authenticated-Sender: a2plcpnl0131.prod.iad2.secureserver.net: support@telium.ca X-Source: X-Source-Args: X-Source-Dir: X-CMAE-Envelope: MS4wfPLGE9zEdtLEixnd8PQqbRvDx3exEgobze3SolIKERGqFU+cmeRfpKsquAV+ATFgDwGQrqATDoec/mmC4c9bkBSmFAnfH1dB3qpf6f5HG89sjz3lYlOm pqnmKLHwN6XovOM2NNZPJE8rwOcPsRLK92nfJTETHA1Gu6/+8QXEFGNN5Nq4XxOnEh9ecM+Hhit0DBZ5hHmmUTBMQ1Wb/tqGhQeVUi2HjeqA54LHPg+rXGsM List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multipart message in MIME format. ------=_NextPart_000_0004_01D3AA61.BE36AC00 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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)? ------=_NextPart_000_0004_01D3AA61.BE36AC00 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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 =3D '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 =3D (boolean)

  =  trigger_file =3D (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)?

 

------=_NextPart_000_0004_01D3AA61.BE36AC00--