| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Chris Purcell <chris(dot)purcell(dot)39(at)gmail(dot)com> |
| Cc: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-bugs(at)postgresql(dot)org, Sunir Shah <sunir(at)sunir(dot)org> |
| Subject: | Re: Unexpected chunk number |
| Date: | 2006-09-12 14:23:05 |
| Message-ID: | 15848.1158070985@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Chris Purcell <chris(dot)purcell(dot)39(at)gmail(dot)com> writes:
> Given that we are where we are, what is the best advice? Can we
> recover the database, given that 99% of the data works? I can happily
> drop the entire contents of the "pagecache" table, as it is
> regenerated on the fly, if that will obviate the problem.
That will get you past the reported problem, but I wonder what other
corruption is lurking ... once you've managed to pg_dump you'd better
inspect the data very carefully.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | gerrit | 2006-09-12 15:26:33 | BUG #2623: query optimizer not using indexes with inheritance and joins |
| Previous Message | Shelby Cain | 2006-09-12 14:07:20 | Re: BUG #2609: server crash at 182 connections still alive. |