| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Garry Saddington <garry(at)schoolteachers(dot)co(dot)uk> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Losing data |
| Date: | 2008-06-19 18:20:26 |
| Message-ID: | 19287.1213899626@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Garry Saddington <garry(at)schoolteachers(dot)co(dot)uk> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shane Ambler | 2008-06-19 18:28:29 | Re: Losing data |
| Previous Message | Garry Saddington | 2008-06-19 18:12:01 | Re: Losing data |