Re: Enabling archive_mode without restart

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>
Cc: "Simon Riggs" <simon(at)2ndQuadrant(dot)com>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Enabling archive_mode without restart
Date: 2008-10-31 16:02:25
Message-ID: 490AE5C1.EE98.0025.0@wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>> "Joshua D. Drake" <jd(at)commandprompt(dot)com> wrote:
> It certainly makes more sense to do this:
>
> archive_mode = on
> pg_ctl reload
>
> archive_mode = off
> pg_ctl reload
>
> versus
>
> archive_command = '/path/to/really/long/archive/string'
> pg_ctl reload
>
> archive_command = '/bin/true'
> pg_ctl reload

Hmmm... If there's no significant performance difference between

archive_mode = on
archive_command = '/bin/true'

and

archive_mode = off
archive_command = '/archive/command/used/during/snapshot/backups'

I could live with diddling the command to control archiving.

It doesn't log anything extra when archive_mode is on?

Why is it safer to change archive_command to a no-op on the fly than
to turn off archive mode?

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2008-10-31 16:10:05 Re: Window Functions: patch for CommitFest:Nov.
Previous Message Alvaro Herrera 2008-10-31 16:00:38 Re: Window Functions: patch for CommitFest:Nov.