From: Hannu Krosing <hannu@tm.ee>
To: Neil Conway <neilc@samurai.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Will LaShell <will@lashell.net>
Cc: Christopher Browne <cbbrowne@acm.org>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: start of transaction (was: Re: [PERFORM] Help with count(*))
Date: Sun, 16 Nov 2003 13:58:08 +0200
Message-ID: <1068983887.17671.10.camel@fuji.krosing.net> (raw)
In-Reply-To: <87isllbcys.fsf@mailbox.samurai.com>
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>
Redirected to -hackers
Neil Conway kirjutas L, 15.11.2003 kell 22:20:
> Tom Lane <tgl@sss.pgh.pa.us> writes:
> > (I believe the previous discussion also agreed that we wanted to
> > postpone the freezing of now(), which currently also happens at
> > BEGIN rather than the first command after BEGIN.)
>
> That doesn't make sense to me: from a user's perspective, the "start
> of the transaction" is when the BEGIN is issued, regardless of any
> tricks we may play in the backend.
For me, the "start of transaction" is not about time, but about grouping
a set of statements into one. So making the exact moment of "start" be
the first statement that actually does something with data seems
perfectly reasonable. If you really need to preserve time, do "select
current_timestamp" and use the result.
> Making now() return the time the current transaction started is
> reasonably logical; making now() return "the time when the first
> command after the BEGIN in the current transaction was issued" makes a
> lot less sense to me.
for me "the time the current transactuion is started" == "the time when
the first command after the BEGIN in the current transaction was issued"
and thus I see no conflict here ;)
Delaying the locking effects of transactions as long as possible can
increase performance overall, not just for pathological clients that sit
on idle open transactions.
Probably the latest time we can start the transaction is ath the start
of executor step after the first statement in a transaction is planned
and optimized.
---------------
Hannu
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: hannu@tm.ee, neilc@samurai.com, tgl@sss.pgh.pa.us, will@lashell.net, cbbrowne@acm.org, pgsql-hackers@postgresql.org
Subject: Re: start of transaction (was: Re: [PERFORM] Help with count(*))
In-Reply-To: <1068983887.17671.10.camel@fuji.krosing.net>
* 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