On Fri, 2007-01-05 at 11:01 +0100, Zeugswetter Andreas ADI SD wrote:

> > > What's the use-case for changing the variable on the fly anyway?  Seems a
> better
> > > solution is just to lock down the setting at postmaster start.
> I guess that the use case is more for a WAL based replicate, that 
> has/wants a different setting. Maybe we want a WAL entry for the change,
> or force a log switch (so you can interrupt the replicate, change it's
> setting
> and proceed with the next log) ?
> Maybe a 3rd mode for replicates that ignores 0 CRC's ?

Well, wal_checksum allows you to have this turned ON for the main server
and OFF on a Warm Standby. 

The recovery process doesn't check for postgresql.conf reloads, so
setting it at server start is effectively the same thing in that case.

  Simon Riggs             
  EnterpriseDB   http://www.enterprisedb.com

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to [EMAIL PROTECTED] so that your
       message can get through to the mailing list cleanly

Reply via email to