> > > > 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.
Ok, so when you need CRC's on a replicate (but not on the master) you
turn it
off during standby replay, but turn it on when you start the replicate
for normal operation.
Andreas
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
