Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and - Mailing list pgsql-hackers

  now agree that the logging is more part of the table than
> the command itself.  Right now we have a COPY LOCK patch, but people are
> going to want to control logging for INSERT INTO ... SELECT, and UPDATE,
> and all sorts of other things, so I think we are best adding an ALTER
> TABLE capability.  I am thinking of this syntax:
> 
>     ALTER TABLE name RELIABILITY option
> 
> where "option" is:
> 
>     DROP [ TABLE ON CRASH ]
>     DELETE [ ROWS ON CRASH ]
>     EXCLUSIVE
>     SHARE

I would say ON FAILURE (Crash just seems way to scary :))

Joshua D. Drake