Postgres Pro
Downloads
Home   >   mailing lists

Thread: Restart or reload after changing the archive_command

Restart or reload after changing the archive_command

From
John Scalia
Date:
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
torecall 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.
--
Jay

Re: Restart or reload after changing the archive_command

From
Guillaume Lelarge
Date:
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.


--

Re: Restart or reload after changing the archive_command

From
John Scalia
Date:
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.


--

Re: Restart or reload after changing the archive_command

From
Shreeyansh dba
Date:
If You want to change archive_mode then you need to restart the server & archive_command need only reload the server.

parameter "archive_mode" cannot be changed without restarting the server
parameter "archive_command" changed to "copy "%p" "D:\arch\%f""
--

Thanks & Regards,

Harshad Adalkonda
Database Administrator

www.shreeyansh.com


On Wed, Oct 8, 2014 at 1:57 AM, John Scalia <jayknowsunix@gmail.com> 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.
--
Jay


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

Re: Restart or reload after changing the archive_command

From
Ray Stell
Date:
On Oct 7, 2014, at 4:27 PM, John Scalia <jayknowsunix@gmail.com> wrote:

> I've been looking online for an answer

http://www.postgresql.org/docs/9.3/interactive/runtime-config-wal.html#RUNTIME-CONFIG-WAL-ARCHIVING
http://www.postgresql.org/docs/9.3/interactive/runtime-config.html

Re: Restart or reload after changing the archive_command

From
Albe Laurenz
Date:
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