Re: [GENERAL] CURRENT_TIMESTAMP

Ross Reedstrom <reedstrm@rice.edu>

From: "Ross J. Reedstrom" <reedstrm@rice.edu>
To: Roland Roberts <roland@astrofoto.org>
Cc: pgsql-sql@postgresql.org, pgsql-general@postgresql.org
Date: 2002-09-24T15:10:03Z
Lists: pgsql-hackers, pgsql-general, pgsql-sql
On Tue, Sep 24, 2002 at 10:55:41AM -0400, Roland Roberts wrote:
> >>>>> "Martijn" == Martijn van Oosterhout <kleptog@svana.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