| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | John Hasler <john(at)dhh(dot)gt(dot)org> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] CURRENT_TIMESTAMP |
| Date: | 2002-09-24 03:17:32 |
| Message-ID: | 200209240317.g8O3HWK29571@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-sql |
John Hasler wrote:
> Bruce Momjian writes:
> > My point is that our current behavior may not be the most intuitive, and
> > that most people may prefer a change.
>
> I would prefer a change.
Yes, I guess that is my point, that we want to make transaction _and_
statement timestamp values available, but most people are going to use
current_timestamp, and most people are going to assume it is statement
time, not transaction time.
Can I add TODO items for this:
o Make CURRENT_TIMESTAMP/now() return statement start time
o Add TRANSACTION_TIMESTAMP to return transaction start time
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-09-24 03:18:18 | Re: [SQL] Monitoring a Query |
| Previous Message | John Hasler | 2002-09-24 02:20:52 | Re: [GENERAL] CURRENT_TIMESTAMP |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-09-24 03:18:18 | Re: [SQL] Monitoring a Query |
| Previous Message | John Hasler | 2002-09-24 02:20:52 | Re: [GENERAL] CURRENT_TIMESTAMP |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-09-24 03:18:18 | Re: [SQL] Monitoring a Query |
| Previous Message | John Hasler | 2002-09-24 02:20:52 | Re: [GENERAL] CURRENT_TIMESTAMP |