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

>     * 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