| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Manfred Koizar <mkoi-pg(at)aon(dot)at>, 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 |
| Subject: | Re: [GENERAL] CURRENT_TIMESTAMP |
| Date: | 2002-09-24 01:53:36 |
| Message-ID: | 200209231853.36530.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-sql |
Tom, Bruce,
> > A possible compromise is to dissociate now() and current_timestamp,
> > allowing the former to be start of transaction and the latter to be
> > start of client command.
>
> I was thinking 'transaction_timestamp' for the transaction start time, and
> current_timestamp for the statement start time. I would equate now()
> with current_timestamp.
May I point out that this will break compatibility for those used to the
current behavior?
--
-Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-09-24 01:59:07 | Conference, training |
| Previous Message | Garo Hussenjian | 2002-09-24 01:43:39 | Output format revisited - booleans |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-09-24 02:01:06 | Re: [GENERAL] CURRENT_TIMESTAMP |
| Previous Message | Martijn van Oosterhout | 2002-09-24 01:19:12 | Re: [SQL] CURRENT_TIMESTAMP |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-09-24 02:01:06 | Re: [GENERAL] CURRENT_TIMESTAMP |
| Previous Message | Martijn van Oosterhout | 2002-09-24 01:19:12 | Re: [SQL] CURRENT_TIMESTAMP |