Horton
Menu

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

Bruce Momjian <pgman@candle.pha.pa.us>

View thread
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: "Joshua D. Drake" <jd@commandprompt.com>
Cc: Martijn van Oosterhout <kleptog@svana.org>, Simon Riggs <simon@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, Greg Stark <gsstark@mit.edu>, Rod Taylor <pg@rbt.ca>, Qingqing Zhou <zhouqq@cs.toronto.edu>, pgsql-hackers@postgresql.org
Date: 2005-12-29T04:09:21Z
Lists: pgsql-hackers 
Joshua D. Drake wrote:
>   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 :))

Agreed, maybe ON RECOVERY.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073