From: Stephan Szabo <sszabo@megazone.bigpanda.com>
To: Greg Stark <gsstark@mit.edu>
Cc: pgsql-hackers@postgresql.org
Subject: Re: start of transaction (was: Re: [PERFORM] Help with
Date: Sun, 16 Nov 2003 23:09:05 -0800 (PST)
Message-ID: <20031116230227.H82963@megazone.bigpanda.com> (raw)
In-Reply-To: <87he13a5hy.fsf@stark.dyndns.tv>
References: <200311141251.38786.mallah@trade-india.com>
<m3ad6zkpgj.fsf@wolfe.cbbrowne.com>
<1068831807.2540.44.camel@fuji.krosing.net>
<3FB52FA7.8060508@lashell.net>
<4987.1068842326@sss.pgh.pa.us>
<87isllbcys.fsf@mailbox.samurai.com>
<1068983887.17671.10.camel@fuji.krosing.net>
<873ccnc49e.fsf@mailbox.samurai.com>
<87he13a5hy.fsf@stark.dyndns.tv>
On Sun, 17 Nov 2003, Greg Stark wrote:
> Neil Conway <neilc@samurai.com> writes:
>
> > What does BEGIN actually do now, from a user's perspective?
>
> I think you're thinking about this all wrong. BEGIN doesn't "do" anything.
> It's not a procedural statement, it's a declaration. It declares that the
> block of statements form a transaction so reads should be consistent and
> failures should be handled in a particular way to preserve data integrity.
>
> Given that declaration and the guarantees it requires of the database it's
> then up to the database to figure out what constraints that imposes on what
> the database can do and still meet the guarantees the BEGIN declaration
> requires. The more clever the database is about minimizing those restrictions
> the better as it means the database can run more efficiently.
>
> For what it's worth, this is how Oracle handles things too. On the
> command-line issuing a BEGIN following a COMMIT is just noise; you're _always_
> in a transaction. A COMMIT ends the previous the transaction and implicitly
> starts the next transaction. But the snapshot isn't frozen until you first
> read from a table.
The earlier portion of the described behavior is AFAICS not complient to
SQL99 at least. COMMIT (without AND CHAIN) terminates a transaction and
does not begin a new one. The new transaction does not begin until a
transaction initiating command (for example START TRANSACTION, CREATE
TABLE, INSERT, ...) is executed. The set of things you can do that aren't
initiating is fairly small admittedly, but it's not a null set.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: sszabo@megazone.bigpanda.com, gsstark@mit.edu, pgsql-hackers@postgresql.org
Subject: Re: start of transaction (was: Re: [PERFORM] Help with
In-Reply-To: <20031116230227.H82963@megazone.bigpanda.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox