Re: Weird prepared stmt behavior

From: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Weird prepared stmt behavior
Date: 2004-05-04 13:12:19
Message-ID: 20040504131219.GB2417@dcc.uchile.cl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 04, 2004 at 12:03:16AM -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
> > Right. But note that Tom wants to distinguish between statements
> > created via PREPARE (which would rollback) from those created via a
> > Prepare message (which wouldn't).
>
> Actually, no, I'd prefer not to make such a distinction; I'd be happy
> with SQL-level PREPARE being nontransactional. I'd be willing to put up
> with that distinction if someone shows it's needed, but so far there's
> not been a really good argument advanced for it, has there?

Will do.

--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"I would rather have GNU than GNOT." (ccchips, lwn.net/Articles/37595/)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2004-05-04 13:17:18 Re: Call for 7.5 feature completion
Previous Message Tom Lane 2004-05-04 12:06:02 Re: inconsistent owners in newly created databases?