| From: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
|---|---|
| To: | Elaine Lindelef <eel(at)cognitivity(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] timestamp weirdness |
| Date: | 2002-02-02 01:03:14 |
| Message-ID: | 3C5B3AD2.32889E18@fourpalms.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> >The timestamp provided as a result of evaluating 'now' is the time of
> >the start of the transaction, not the instantaneous wall clock time (if
> >you want the latter there is a function to provide it).
> We are now thinking that what is happening is that the first write
> may have a long open transaction.
> What is the function you mention to provide instantaneous time?
lockhart=# select timestamp 'now', cast(timeofday() as timestamp);
?column? | ?column?
------------------------+---------------------------
2002-02-01 17:01:19-08 | 2002-02-01 17:01:31.21-08
hth
- Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Explorer | 2002-02-02 09:24:55 | Re: Few questions |
| Previous Message | Darren Ferguson | 2002-02-01 22:19:03 | Re: Few questions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2002-02-02 04:00:50 | Re: PostgreSQL Final Release ... Monday? |
| Previous Message | Tom Lane | 2002-02-01 23:11:51 | Re: Syscaches should store negative entries, too |