pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Hannu Krosing <hannu@tm.ee>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Neil Conway <neilc@samurai.com>
Cc: Will LaShell <will@lashell.net>
Cc: Christopher Browne <cbbrowne@acm.org>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: start of transaction (was: Re: [PERFORM] Help with count(*))
Date: Mon, 17 Nov 2003 19:52:51 -0500 (EST)
Message-ID: <200311180052.hAI0qpw10716@candle.pha.pa.us> (raw)
In-Reply-To: <1069064346.20092.27.camel@fuji.krosing.net>

Hannu Krosing wrote:
> Bruce Momjian kirjutas E, 17.11.2003 kell 02:31:
> 
> > Defining now() as the first call seems pretty arbitrary to me.  I can't
> > think of any time-based interface that has that API.  And what if a
> > trigger called now() in an earlier query and you didn't even know about
> > it.
> 
> That would be OK. The whole point of that previous discussion was to
> have now() that returns the same value over the span of the whole
> transaction.

I think my issue is that there isn't any predictable way for a user to
know when the now() time is recorded.  By using start of transaction, at
least we know for sure the point in time it is showing.

> It would be even better to have now() that returns the time current
> transaction is COMMITted as this is the time other backend become aware
> of it ;)

True, but implementing that would be very hard.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073



view thread (13+ messages)  latest in thread

Message-ID: <200311180052.hAI0qpw10716@candle.pha.pa.us>
Permalink:  ../200311180052.hAI0qpw10716@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200311180052.hAI0qpw10716@candle.pha.pa.us

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: pgman@candle.pha.pa.us, hannu@tm.ee, tgl@sss.pgh.pa.us, neilc@samurai.com, will@lashell.net, cbbrowne@acm.org, pgsql-hackers@postgresql.org
  Subject: Re: start of transaction (was: Re: [PERFORM] Help with count(*))
  In-Reply-To: <200311180052.hAI0qpw10716@candle.pha.pa.us>
  References: <1069064346.20092.27.camel@fuji.krosing.net> <200311180052.hAI0qpw10716@candle.pha.pa.us>

* 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