Horton
Menu

Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and

Christopher Kings-Lynne <chriskl@familyhealth.com.au>

View thread
From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Simon Riggs <simon@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, Martijn van Oosterhout <kleptog@svana.org>, Greg Stark <gsstark@mit.edu>, Rod Taylor <pg@rbt.ca>, Qingqing Zhou <zhouqq@cs.toronto.edu>, pgsql-hackers@postgresql.org
Date: 2006-02-07T02:24:31Z
Lists: pgsql-hackers 
> 	* Allow WAL logging to be turned off for a table, but the table
> 	  might be dropped or truncated during crash recovery [walcontrol]
> 	
> 	  Allow tables to bypass WAL writes and just fsync() dirty pages on
> 	  commit.  This should be implemented using ALTER TABLE, e.g. ALTER
> 	  TABLE PERSISTENCE [ DROP | TRUNCATE | DEFAULT ].  Tables using
> 	  non-default logging should not use referential integrity with
> 	  default-logging tables.  A table without dirty buffers during a
> 	  crash could perhaps avoid the drop/truncate.

This would be such a sweet feature for website session tables...

Chris