Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1W9zWK-0005Zu-Mq for pgsql-admin@arkaria.postgresql.org; Sun, 02 Feb 2014 16:03:44 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1W9zWK-0004wK-6o for pgsql-admin@arkaria.postgresql.org; Sun, 02 Feb 2014 16:03:44 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1W9zWJ-0004wE-BH for pgsql-admin@postgresql.org; Sun, 02 Feb 2014 16:03:43 +0000 Received: from mail-ig0-f178.google.com ([209.85.213.178]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1W9zWG-0001Xn-9y for pgsql-admin@postgresql.org; Sun, 02 Feb 2014 16:03:42 +0000 Received: by mail-ig0-f178.google.com with SMTP id uq10so2693388igb.5 for ; Sun, 02 Feb 2014 08:03:39 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type; bh=ICZMUNJRSfiL+PntcrOkH5uwNqsDIN+RgysET4za8kw=; b=Mtt4iVZy5a9GwV7/dWmjTImJL0gaoWgsirXIjkXw9D02goqNvsvqOsq24pnBm8ilOJ XXPru9pKgX867/g/xEcsBAiFeqmgx+nMtxnGpteOeBdSK4JyG9kxubJrXRUM96aHRxya +Z58ZZSzF9jpLXivWao6AJruA2B9ZVZbCf57lW3HbfbVLAoD0FbZ0kClA5t7hVNaxrvw hRhdLIrHv5E+d943AmsID7oVfvNlXFMMY79dj220CaVKoG3k+Uso/7Jv531+NQDO4QTE uhCZybRyMcLcce6Axyr3o+fBqQQEt8vHrVrFQ2uu6sImXY1zbTKjaDugqDa5jRMNt5k4 RSnA== X-Gm-Message-State: ALoCoQnrmndDMZ34lJtG/wNKTj3TMJYq5h5L8LPW9P594aoNHhEG1Ar0GOvgbFFh7O1g250gkyw+ X-Received: by 10.50.128.137 with SMTP id no9mr8229450igb.36.1391357019435; Sun, 02 Feb 2014 08:03:39 -0800 (PST) Received: from Kevins-MacBook-Pro.local ([67.148.186.194]) by mx.google.com with ESMTPSA id u1sm20591068ige.1.2014.02.02.08.03.30 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 02 Feb 2014 08:03:34 -0800 (PST) Message-ID: <52EE6C51.3010708@consistentstate.com> Date: Sun, 02 Feb 2014 09:03:29 -0700 From: CS DBA User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: =?UTF-8?B?U3RyYWhpbmphIEt1c3R1ZGnEhw==?= CC: pgsql-admin Subject: Re: Cannot change archive_command with a reload References: <52EE69AF.4030709@consistentstate.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------010905070500070902040909" X-Pg-Spam-Score: -2.6 (--) 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. --------------010905070500070902040909 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit We're running version 9.2.4, on Redhat 5.1 I have tried changing the config file and running "service postgresql-9.2 reload" I've also tried (as user postgres): pg_ctl -D /var/lib/pgsql/9.2/data reload no luck with either approach On 2/2/14, 8:58 AM, Strahinja Kustudić wrote: > What version of Postgres are you using? What OS? Have you tried > editing the archive_command in postgresql.conf and then reload? > > Strahinja Kustudić| Lead System Engineer | Nordeus > > > On Sun, Feb 2, 2014 at 4:52 PM, CS DBA > wrote: > > Hi all; > > we have a cluster running with an archive command that is failing. > I tried a reload and the value does not change > > Tried a set_config and I get this error: > > select set_config ('archive_command', 'cp %p /data/wal_tmp/%f && > mv /data/wal_tmp/%f /data/wal/&f', 'false'); > ERROR: parameter "archive_command" cannot be changed now > > > Thoughts? > > Thanks in advance > > > -- > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org > ) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin > > --------------010905070500070902040909 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
We're running version 9.2.4,  on Redhat 5.1
I have tried changing the config file and running "service postgresql-9.2 reload"

I've also tried (as user postgres): pg_ctl -D /var/lib/pgsql/9.2/data reload

no luck with either approach




 On 2/2/14, 8:58 AM, Strahinja Kustudić wrote:
What version of Postgres are you using? What OS? Have you tried editing the archive_command in postgresql.conf and then reload?

Strahinja Kustudić
| Lead System Engineer | Nordeus


On Sun, Feb 2, 2014 at 4:52 PM, CS DBA <cs_dba@consistentstate.com> wrote:
Hi all;

we have a cluster running with an archive command that is failing.
I tried a reload and the value does not change

Tried a set_config and I get this error:

select set_config ('archive_command', 'cp %p /data/wal_tmp/%f && mv /data/wal_tmp/%f /data/wal/&f', 'false');
ERROR:  parameter "archive_command" cannot be changed now


Thoughts?

Thanks in advance


--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin


--------------010905070500070902040909--