Re: [GENERAL] CURRENT_TIMESTAMP

From: "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>
To: Roland Roberts <roland(at)astrofoto(dot)org>
Cc: pgsql-sql(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] CURRENT_TIMESTAMP
Date: 2002-09-24 15:10:03
Message-ID: 20020924151003.GC7612@rice.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers pgsql-sql

On Tue, Sep 24, 2002 at 10:55:41AM -0400, Roland Roberts wrote:
> >>>>> "Martijn" == Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
>
> Martijn> Well, what I would suggest is that when you wrap several
> Martijn> statements into a single transaction with begin/commit,
> Martijn> the whole lot could be considered a single statement
> Martijn> (since they form an atomic transaction so in a sense they
> Martijn> are all executed simultaneously). And hence Postgresql is
> Martijn> perfectly compliant.
>
> FWIW, and not that I am an Oracle fan :-), Oracle seems to interpret
> this the same way when using a "select sysdate from dual" inside a
> transaction.

Oh, interesting datapoint. Let me get this clear - on oracle, the
equivalent of:

BEGIN;
SELECT current_timestamp;
<go off to lunch, come back>
SELECT current_timestamp;
END;

will give two identical timestamps?

Ross

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stephan Szabo 2002-09-24 15:16:28 Re: Number of disk pages obtained by explain analyze (fwd)
Previous Message Ross J. Reedstrom 2002-09-24 15:07:51 Re: [GENERAL] CURRENT_TIMESTAMP

Browse pgsql-hackers by date

  From Date Subject
Next Message Yury Bokhoncovich 2002-09-24 15:10:22 Re: Default privileges for 7.3
Previous Message Ross J. Reedstrom 2002-09-24 15:07:51 Re: [GENERAL] CURRENT_TIMESTAMP

Browse pgsql-sql by date

  From Date Subject
Next Message Ross J. Reedstrom 2002-09-24 15:19:49 Re: [GENERAL] CURRENT_TIMESTAMP
Previous Message Ross J. Reedstrom 2002-09-24 15:07:51 Re: [GENERAL] CURRENT_TIMESTAMP