Re: Nested Transaction TODO list

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(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-10 01:27:59
Message-ID: 1398.1089422879@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> [shrug...] I'd counsel leaving this as-is.

> What information are we loosing by having START and BEGIN use the same
> nodes? Knowing what keyword they used to start the transaction?

Exactly.

> Seems that would only be important if we wanted them to behave
> differently, which we don't, I think.

Whether we want them to behave differently or not, we need to preserve
the difference. The prior cases where the parser smashed two different
inputs into the same parse tree have all been "because it doesn't
matter", and sure enough we've usually eventually decided it did matter.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2004-07-10 01:29:52 Re: More vacuum.c refactoring
Previous Message Bruce Momjian 2004-07-10 01:23:54 Re: thread safety tests