pgsql: Disable full_page_writes, because turning it off risks causing

Started by Tom Laneover 20 years ago2 messagescomitters
Jump to latest
#1Tom Lane
tgl@sss.pgh.pa.us

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)

#2Bruce Momjian
bruce@momjian.us
In reply to: Tom Lane (#1)
Re: pgsql: Disable full_page_writes, because turning it

Added to TODO:

* Re-enable the GUC full_page_writes in 8.2 when reliability issues have
been addressed

---------------------------------------------------------------------------

Tom Lane wrote:

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)

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +