Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1X5bP4-0000r4-NF for pgsql-admin@arkaria.postgresql.org; Fri, 11 Jul 2014 14:02:22 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1X5bP4-0006Ib-4D for pgsql-admin@arkaria.postgresql.org; Fri, 11 Jul 2014 14:02:22 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1X5bP2-0006Ga-KQ for pgsql-admin@postgresql.org; Fri, 11 Jul 2014 14:02:20 +0000 Received: from mail-yh0-x22a.google.com ([2607:f8b0:4002:c01::22a]) by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1X5bOt-0002WE-Eh for pgsql-admin@postgresql.org; Fri, 11 Jul 2014 14:02:19 +0000 Received: by mail-yh0-f42.google.com with SMTP id i57so421860yha.29 for ; Fri, 11 Jul 2014 07:01:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=oFoK6L9RvuHjOys/184ZZjXDmpCHLwsRjH52Y5iII2c=; b=1DUKfwkGp2ra85V8igLAm1cTy3Eqx8JU7+ug3fadY+cWdfBrYOJEmiar4rXAtj1Plx uurf1N5/X2BwRGiIZuUzoGD8Z3KbtKrrtGmtHVvnKLIP14Ve46QJ/WVn7RY17weO/HvV 7jTKZtgeu5A6h5S4pQDFSuu72XSYvCudshQd4HcOfbdHmMfhQyNsBEYClFUGJ4+fjkI9 GBgwIKpEVvV9Akcgq8JG+ZKcb6R2IG351zsxLsHyxSKyf/x33OBeYkBkm9zI1dDDIuf/ qhAGeAJhdg4znq2GNtdDkaVrMmEiATmgjVdMLND5wAoJmUIQ1uuF90u3+j/iamUtqfuk mScQ== X-Received: by 10.236.129.115 with SMTP id g79mr45424099yhi.86.1405087309489; Fri, 11 Jul 2014 07:01:49 -0700 (PDT) Received: from [192.168.254.5] (h77.89.102.166.static.ip.windstream.net. [166.102.89.77]) by mx.google.com with ESMTPSA id d46sm5208229yha.10.2014.07.11.07.01.48 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Jul 2014 07:01:49 -0700 (PDT) Message-ID: <53BFEE46.9050301@gmail.com> Date: Fri, 11 Jul 2014 10:01:42 -0400 From: John Scalia User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "pgsql-admin@postgresql.org" Subject: postgresql checking return status of archive_command? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org hi all, First off, my thanks to everyone who responded to my last post regarding copying WAL segments to 2 standby servers. My script is working wonderfully now, but I have a followup question like the subject line. Does postgresql or any of its child processes check the return code of the command executed in the archive_command and does it log anything if that return code is NOT zero? I've been trying to think of easy ways to force an error to test, but thought I'd ask first. TIA, Jay -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin