| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Aniket Kulkarni <aniket_kulkarni(at)persistent(dot)co(dot)in> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Information about XLogWrite |
| Date: | 2002-02-19 21:06:09 |
| Message-ID: | 20376.1014152769@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Aniket Kulkarni <aniket_kulkarni(at)persistent(dot)co(dot)in> writes:
> Recently I got this error while the database was starting up. :
> FATAL 2: XLogWrite: writerequest is past end of log
> And the database did not startup, and finally I had to do a
> pg_resetxlog. I tried going through the code which gave
> this error but I was unable to comprehend much.
> Could anyone tell me how exactly this error is caused.
XLogWrite? Not XLogFlush? That'd be a new one on me. Too bad you
flushed the broken xlog, I would have liked to look at it.
There is a known failure path (believed fixed in 7.2) whereby garbage
data in pg_log pages can lead to XLogFlush startup failures.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2002-02-19 21:07:55 | Re: pg_dump: use ALTER TABLE for PKs |
| Previous Message | Neil Conway | 2002-02-19 20:59:44 | Re: questions on ALTER TABLE ... OWNER |