From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Mike Mascari <mascarm(at)mascari(dot)com> |
Cc: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: autocommit vs TRUNCATE et al |
Date: | 2002-10-19 02:15:32 |
Message-ID: | 200210190215.g9J2FWZ11631@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Mike Mascari wrote:
> Gavin Sherry wrote:
> > On Fri, 18 Oct 2002, Tom Lane wrote:
> >
> >
> >>Anyone see a way out of this catch-22? If not, which is the least
> >>bad alternative?
> >
> >
> > Ultimately, fix TRUNCATE to be transaction safe. This is non-trivial,
> > I know :-).
> >
> > Regardless, the first option seems the less of the two evils.
>
> Even though TRUNCATE was modeled after Oracle's TRUNCATE and
> Oracle's TRUNCATE commits the running tx, truncates the
> relation, and starts a new tx, regardless of whether or not
> TRUNCATE is the first statement of the tx?
That seems just too harsh to me. I think we should impose some
structure to it, though we will have compatibility issues.
--
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 | Bruce Momjian | 2002-10-19 02:30:40 | /contrib/retep to gborg |
Previous Message | Bruce Momjian | 2002-10-19 02:09:35 | Re: [HACKERS] ALTER TABLE ... ADD COLUMN |