Garry Saddington <[EMAIL PROTECTED]> writes:
> Oh, and the problem has been intermittant. Another
> thing that happened this morning is that Postgres had today as 18/06/2008
> when in fact it was 19/06/2008 and the OS reported this correctly.
Two theories about that one:
1. Postgres' timezone setting is far away from where you are.
2. You were in a transaction that had been open since yesterday.
now() and related functions show time of transaction start.
#2 is interesting since forgetting to commit an open transaction might
also explain the "data loss" complaint.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
