Re: Changing behavior of BEGIN...sleep...do something...COMMIT

From: Jon Jensen <jon(at)endpoint(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Changing behavior of BEGIN...sleep...do something...COMMIT
Date: 2003-03-29 04:54:05
Message-ID: Pine.LNX.4.50.0303290452550.3394-100000@louche.swelter.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 28 Mar 2003, Tom Lane wrote:

> It seems to me that it'd be fairly easy to make BEGIN cause only
> a local state change in the backend; the actual transaction need not
> start until the first subsequent command is received.
[snip]
> In a very real sense, the transaction snapshot defines "when the
> transaction starts" --- so shouldn't now() agree?
>
> If we did both of these things, then the negatives of doing an early
> BEGIN would pretty much vanish, and we'd not need to complain that these
> client libraries are broken.
>
> Comments?

Both ideas sound like a win to me.

Jon

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Key88 SF 2003-03-29 06:30:05 extract(timezone_hour) problem
Previous Message Tom Lane 2003-03-29 04:13:28 Changing behavior of BEGIN...sleep...do something...COMMIT