"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> On Fri, Mar 09, 2007 at 04:57:18PM +0000, Simon Riggs wrote:
>> It's certainly a quicker fix. Unless others object, I'll set
>> archive_command to only be changeable at server startup.
> I think the docs should also explain why it's server-start only, since
> if someone wanted to they could circumvent the behavior by having
> archive_command call a shell script that changes it's behavior.
Um, what's the problem with that? The concern was about whether PG
would produce consistent WAL output, not whether the archive_command
actually needed to do anything.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
