| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <gsstark(at)mit(dot)edu>, Rod Taylor <pg(at)rbt(dot)ca>, Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and |
| Date: | 2005-12-29 04:09:21 |
| Message-ID: | 200512290409.jBT49LD13611@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2005-12-29 04:53:15 | Re: sending mail from Postgres |
| Previous Message | Joshua D. Drake | 2005-12-29 03:05:30 | Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and |