Re: Nested Transaction TODO list

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Nested Transaction TODO list
Date: 2004-07-06 17:09:12
Message-ID: 200407061709.i66H9CF21794@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
> > Why does START have a different Node from BEGIN anyway? This seems to
> > be a leftover from when people thought they should behave differently.
> > They are the same now, so there's no point in distinguishing them, or is it?
>
> [shrug...] I'd counsel leaving this as-is. We've practically always
> regretted it when we made the parser discard information about what
> the user typed. For instance, I was just reminded yesterday that we
> really ought to distinguish SortClauses created due to user ORDER BY
> clauses from those created because the parser silently added 'em.

What information are we loosing by having START and BEGIN use the same
nodes? Knowing what keyword they used to start the transaction? Seems
that would only be important if we wanted them to behave differently,
which we don't, I think.

--
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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2004-07-06 17:10:44 Re: Postgresql on SAN
Previous Message Bruno Wolff III 2004-07-06 17:09:03 Re: Postgresql on SAN