Re: Restart or reload after changing the archive_command

From: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "John Scalia *EXTERN*" <jayknowsunix(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Restart or reload after changing the archive_command
Date: 2014-10-08 08:12:15
Message-ID: A737B7A37273E048B164557ADEF4A58B17D60F9F@ntex2010a.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

John Scalia wrote:
> 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 already got the answer (reload), but since you mentioned the documentation,
it is a bit tricky in that respect:
If a configuration parameter requires a server restart, the documentation will say
"This parameter can only be set at server start."
Since the archive_command documentation does *not* state that, it can be changed
with a reload.

Yours,
Laurenz Albe

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Stuart Bishop 2014-10-08 12:14:44 Re: Suspending postgresql during heavy load
Previous Message Mohinder Raina 2014-10-07 23:19:42 Re: PostgreSQL Training