| 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: | John Hasler <john(at)dhh(dot)gt(dot)org>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] CURRENT_TIMESTAMP |
| Date: | 2002-09-24 03:44:37 |
| Message-ID: | 9823.1032839077@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-sql |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> 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
I object to both of those as phrased. If you have already unilaterally
determined the design of this feature change, then go ahead and put that
in. But I'd suggest
o Revise current-time functions to allow access to statement
start time
which doesn't presuppose the vote about how to do it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-09-24 03:52:55 | Re: [GENERAL] CURRENT_TIMESTAMP |
| Previous Message | Bruce Momjian | 2002-09-24 03:37:45 | Re: [GENERAL] CURRENT_TIMESTAMP |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gavin Sherry | 2002-09-24 03:49:46 | Web site |
| Previous Message | Bruce Momjian | 2002-09-24 03:37:45 | Re: [GENERAL] CURRENT_TIMESTAMP |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-09-24 03:52:55 | Re: [GENERAL] CURRENT_TIMESTAMP |
| Previous Message | Bruce Momjian | 2002-09-24 03:37:45 | Re: [GENERAL] CURRENT_TIMESTAMP |