| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bill Moran <wmoran(at)potentialtech(dot)com> |
| Cc: | Rob Richardson <Rob(dot)Richardson(at)rad-con(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL service won't start after bad computer time |
| Date: | 2011-06-03 16:04:17 |
| Message-ID: | 28377.1307117057@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bill Moran <wmoran(at)potentialtech(dot)com> writes:
> On 6/3/11 8:52:15 AM, Rob Richardson wrote:
>> I did some testing involving changing a computers time, and left the
>> time one year early (6/3/2010 instead of 2011). The PostgreSQL service
>> now will not start up. Heres what the log says:
>>
>> 2011-06-03 08:46:56 EDTLOG: record with zero length at 9/8E080968
>> 2011-06-03 08:46:56 EDTLOG: redo done at 9/8E07FA78
>> 2011-06-03 08:46:56 EDTLOG: last completed transaction was at log time
>> 2010-06-03 08:11:17.531-04
>> 2011-06-03 08:46:56 EDTFATAL: xlog flush request 18/A2BE3510 is not
>> satisfied --- flushed only to 9/8E080968
>> 2011-06-03 08:46:56 EDTCONTEXT: writing block 0 of relation global/1261_vm
>> How do we recover from this?
> Reset the time to be correct.
I don't think that failure has anything to do with system clock time.
It looks more like filesystem corruption or missing pg_xlog files.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Boreham | 2011-06-03 16:20:12 | Re: Mixed up protocol packets in server response? |
| Previous Message | Bill Moran | 2011-06-03 14:59:19 | Re: PostgreSQL service won't start after bad computer time |