| From: | "Gregory Wood" <gregw(at)com-stock(dot)com> |
|---|---|
| To: | "Alex Pilosov" <alex(at)pilosoft(dot)com> |
| Cc: | "PostgreSQL-General" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Re: timestamp goober |
| Date: | 2001-02-08 18:04:29 |
| Message-ID: | 009901c091f9$b4b26bd0$7889ffcc@comstock.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Oh, I just made sure that I started a new transaction :)
I actually prefer that timestamps are handled that way... once I realized
*why* I had triggered INSERTs that were stamped 45 minutes earlier than I
thought they should have been.
Greg
> Yes, and that's a feature :)
>
> If you want a wall clock time, use timenow()
> > I noticed that timestamps (in my case CURRENT_TIMESTAMP) are taken from
the
> > beginning of a transaction. You didn't mention how you were accessing
the
> > database, but if you were updating everything inside the same
transaction,
> > everything would be timestamped with the time that transaction began.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Pilosov | 2001-02-08 18:27:27 | Re: Re: [SQL] Query never returns ... |
| Previous Message | Alex Pilosov | 2001-02-08 17:50:02 | Re: Re: timestamp goober |