> > >>> Recovery can occur with/without same setting of wal_checksum, to
> > >>> complications from crashes immediately after turning GUC on.
> > >> 
> > >> Surely not.  Otherwise even the "on" setting is not really a
> > 
> > > Only when the CRC is exactly zero, which happens very very rarely.
> > 
> > "It works most of the time" doesn't exactly satisfy me.  What's the


> > use-case for changing the variable on the fly anyway?  Seems a
> > 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
and proceed with the next log) ?

Maybe a 3rd mode for replicates that ignores 0 CRC's ?


---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Reply via email to