Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Xbbhz-0003Nz-Pg for pgsql-admin@arkaria.postgresql.org; Tue, 07 Oct 2014 20:50:12 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Xbbhz-0000pP-97 for pgsql-admin@arkaria.postgresql.org; Tue, 07 Oct 2014 20:50:11 +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 1Xbbhx-0000oj-Lv for pgsql-admin@postgresql.org; Tue, 07 Oct 2014 20:50:10 +0000 Received: from mail-yk0-x22a.google.com ([2607:f8b0:4002:c07::22a]) by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1Xbbht-0005am-BS for pgsql-admin@postgresql.org; Tue, 07 Oct 2014 20:50:08 +0000 Received: by mail-yk0-f170.google.com with SMTP id 20so3240676yks.1 for ; Tue, 07 Oct 2014 13:50:03 -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:cc:subject :references:in-reply-to:content-type; bh=KW6Aab52EjTzTFCb4xz4nnws56NUFEYO1FqRpGr4Ga8=; b=hQotuv/AZKRzSef11nO4dhPFATQJK9s1d3ZA7Oe0ouwOpeyrCr2BKkfdxQ3y2fJxKw zPuV2GQBvfH1tuGBE2UCiW3knwn6BseIdn6HmNhdp8N0F9OR08MudNh4fmS3+mIsJSl7 lhFfCbHCe349P84CH7dr5LlYmt5vxtiGocd6gVuxXc1u+/GltNs+xbcRmkg2SA1wzBJF iDwYay9HX2xoxTvZp8Tg8ZAqWRobQG/cZX+ONaPMxR7wUe58lL3YiWqxHcYUdyCg7XZz QCdwUG2C5tGpubTp4+KZNLxdmQ7MfdGVSAHk/kiGk6miaKyfNrMlpIXsk+mtxAdqZl+m OKjQ== X-Received: by 10.236.150.19 with SMTP id y19mr8610196yhj.94.1412715002985; Tue, 07 Oct 2014 13:50:02 -0700 (PDT) Received: from [192.168.254.2] (h77.89.102.166.static.ip.windstream.net. [166.102.89.77]) by mx.google.com with ESMTPSA id 26sm6163042yhw.51.2014.10.07.13.50.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 Oct 2014 13:50:02 -0700 (PDT) Message-ID: <543451FA.2060503@gmail.com> Date: Tue, 07 Oct 2014 16:50:02 -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: Guillaume Lelarge CC: "pgsql-admin@postgresql.org" Subject: Re: Restart or reload after changing the archive_command References: <54344C9E.9020508@gmail.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------020109050705010207070208" 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 This is a multi-part message in MIME format. --------------020109050705010207070208 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Thanks, Guillaume, I was hoping I remembered that correctly. On 10/7/2014 4:32 PM, Guillaume Lelarge wrote: > 2014-10-07 22:27 GMT+02:00 John Scalia >: > > I've been looking online for an answer, as my test environment is currently unavailable due to an upgrade, but while I know ('cuz it says in the conf file) that a restart is > required when you change "archive_mode", is a restart or a reload required if the "archive_command" is changed? I seem to recall previously that I issued a reload after I > changed this parameter and I saw in the logs that the new value had been recorded, but I'm not certain. > > > You just need a reload. > > > -- > Guillaume. > http://blog.guillaume.lelarge.info > http://www.dalibo.com --------------020109050705010207070208 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Thanks, Guillaume, I was hoping I remembered that correctly.

On 10/7/2014 4:32 PM, Guillaume Lelarge wrote:
2014-10-07 22:27 GMT+02:00 John Scalia <jayknowsunix@gmail.com>:
I've been looking online for an answer, as my test environment is currently unavailable due to an upgrade, but while I know ('cuz it says in the conf file) that a restart is required when you change "archive_mode", is a restart or a reload required if the "archive_command" is changed? I seem to recall previously that I issued a reload after I changed this parameter and I saw in the logs that the new value had been recorded, but I'm not certain.

You just need a reload.


--

--------------020109050705010207070208--