On Thu, 2007-01-04 at 10:00 -0500, Tom Lane wrote:
> "Simon Riggs" <[EMAIL PROTECTED]> writes:
> > In this thread, I outlined an idea for reducing cost of WAL CRC checking
> > http://archives.postgresql.org/pgsql-hackers/2006-10/msg01299.php
> > wal_checksum = on (default) | off
> This still seems awfully dangerous to me.


> > Recovery can occur with/without same setting of wal_checksum, to avoid
> > complications from crashes immediately after turning GUC on.
> Surely not.  Otherwise even the "on" setting is not really a defense.

Only when the CRC is exactly zero, which happens very very rarely.

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

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not

Reply via email to