Is this because of time stamp caching and/or transaction coherency
issues?
Greg
On Mon, 2002-09-30 at 10:02, Bruce Momjian wrote:
>
> CURRENT_TIMESTAMP returns the time of the transaction start, not the
> statement start. We are currently discussing on hackers whether this is
> correct or not. We don't currently allow you to access the statement
> start time. Sorry.
>
> ---------------------------------------------------------------------------
>
> Guido Staub wrote:
> > Hi all,
> > I'm trying the following:
> > BEGIN;
> > select current_timestamp into mytable;
> > .
> > some queries
> > .
> > insert current timestamp into mytable;
> > COMMIT;
> > When I call this with the \i <filename> command, all is working fine,
> > but the two current_timestamp entries are the same, there is no
> > difference between them but there should. So I've tried:
> > BEGIN;
> > select current_timestamp into mytable;
> > .
> > some queries
> > .
> > COMMIT;
> > BEGIN;
> > insert current_timestamp into mytable;
> > COMMIT;
> > and now the entries are different.
> > I think that the accuracy is not good enough because I've started two
> > BEGIN statements and some time is elapsing between them. Am I right?
> > Or does anybody know a better solution to store the elapsed time after
> > some queries without writing some code in C or JAVA?
> >
> > Thanks in advance
> > Guido Staub
>
> --
> 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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
