pgsql: Disable full_page_writes, because turning it off risks causing - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Disable full_page_writes, because turning it off risks causing
Date
Msg-id 20060328220126.0E03411F65DE@postgresql.org
Whole thread Raw
Responses Re: pgsql: Disable full_page_writes, because turning it  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-committers
Log Message:
-----------
Disable full_page_writes, because turning it off risks causing crash-recovery
failures even when the hardware and OS did nothing wrong.  Per recent analysis
of a problem report from Alex Bahdushka.

For the moment I've just diked out the test of the parameter, rather than
removing the GUC infrastructure and documentation, in case we conclude that
there's something salvageable there.  There seems no chance of it being
resurrected in the 8.1 branch though.

Tags:
----
REL8_1_STABLE

Modified Files:
--------------
    pgsql/doc/src/sgml:
        config.sgml (r1.36.2.2 -> r1.36.2.3)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/config.sgml.diff?r1=1.36.2.2&r2=1.36.2.3)
    pgsql/src/backend/access/transam:
        xlog.c (r1.222.2.2 -> r1.222.2.3)

(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c.diff?r1=1.222.2.2&r2=1.222.2.3)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Disable full_page_writes, because turning it off risks causing
Next
From: jwp@pgfoundry.org (James William Pye)
Date:
Subject: python - be: Do cleanup on only commit and abort.