| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Manfred Koizar <mkoi-pg(at)aon(dot)at> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Aaron Held <aaron(at)MetroNY(dot)com>, Roberto Mello <rmello(at)cc(dot)usu(dot)edu>, Neil Conway <neilc(at)samurai(dot)com>, pgsql-sql(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [SQL] Monitoring a Query |
| Date: | 2002-09-23 17:05:42 |
| Message-ID: | 22827.1032800742@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-sql |
Manfred Koizar <mkoi-pg(at)aon(dot)at> writes:
> This has been discussed before and I know I'm going to get flamed for
> this, but IMHO having now() (which is a synonym for CURRENT_TIMESTAMP)
> return the start time of the current transaction is a bug, or at least
> it is not conforming to the standard.
As you say, it's been discussed before. We concluded that the spec
defines the behavior as implementation-dependent, and therefore we
can pretty much do what we want.
If you want exact current time, there's always timeofday().
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Alberer | 2002-09-23 17:34:06 | delete operation with "where XXX in" |
| Previous Message | Manfred Koizar | 2002-09-23 17:01:01 | Re: [SQL] Monitoring a Query |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2002-09-23 18:50:09 | Re: Temp tables and LRU-K caching |
| Previous Message | Manfred Koizar | 2002-09-23 17:01:01 | Re: [SQL] Monitoring a Query |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manfred Koizar | 2002-09-23 19:02:00 | Re: [SQL] CURRENT_TIMESTAMP |
| Previous Message | Manfred Koizar | 2002-09-23 17:01:01 | Re: [SQL] Monitoring a Query |