| From: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
|---|---|
| To: | Elaine Lindelef <eel(at)cognitivity(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: timestamp weirdness |
| Date: | 2002-02-01 04:14:02 |
| Message-ID: | 3C5A160A.89B8C17A@fourpalms.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
...
> The oid correctly reflects the order of the insertion of the rows...
> but look at the timestamp - the last row has a timestamp _2 minutes
> before_ the previous row. How could this be happening? We know row
> 69719 was inserted _after_ 69718, by probably about 30 seconds.
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).
So, the times will reflect the time the transaction was started, while
the OID will reflect the order in which the insert/update actually
happened within the transaction.
hth
- Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Syd Alsobrook | 2002-02-01 04:34:18 | Re: System commands |
| Previous Message | Elaine Lindelef | 2002-02-01 02:20:47 | timestamp weirdness |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-02-01 05:28:41 | Re: Per-database and per-user GUC settings |
| Previous Message | Elaine Lindelef | 2002-02-01 02:20:47 | timestamp weirdness |