From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Guido Staub <staub(at)gik(dot)uni-karlsruhe(dot)de>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: current_timestamp after queries |
Date: | 2002-09-30 15:29:59 |
Message-ID: | 21610.1033399799@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Yes, timeofday() will work, but it can change during the statement, right?
For what he was doing, it seemed perfectly acceptable.
This comes back to the point I've been making during the pghackers
discussion: start-of-transaction time has clear uses, and
exact-current-time has clear uses, but it's not nearly as obvious
why you'd need start-of-statement time in preference to either of
the others.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-09-30 15:34:57 | Need Oracle 9 tester. was Re: current_timestamp after queries |
Previous Message | Bruce Momjian | 2002-09-30 15:17:09 | Re: [HACKERS] current_timestamp after queries |
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2002-09-30 15:30:48 | Re: 7.2.3 fixes (was Re: Cause of missing pg_clog files) |
Previous Message | Bruce Momjian | 2002-09-30 15:29:07 | Re: 7.2.3 fixes (was Re: Cause of missing pg_clog files) |