| From: | "Anand Kumar, Karthik" <Karthik(dot)AnandKumar(at)classmates(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Best way to sync possibly corrupted data? |
| Date: | 2013-12-19 21:28:37 |
| Message-ID: | CED8A503.C59A2%karthik.anandkumar@memorylane.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
HI,
We have an issue with possibly corrupt data in our postgresql server. Errors like:
ERROR: index "photos_p00_n2" contains unexpected zero page at block 0
ERROR: invalid page header in block 12707 of relation pg_tblspc/5020557/PG_9.1_201105231/16393/9014673
Thanks to all the suggestions from this list. We are in the process of moving our database out to a different server, and we'll then set zero_dameged_pages to on, run a full vacuum and reindex.
The question I have is – what is the best method to transfer the data over to ensure we don't copy over bad/corrupt data? I would think a filesystem based copy (rsync, etc) should be avoided, and a pg_dump with a new initdb is best?
Thanks,
Karthik
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergey Konoplev | 2013-12-19 21:39:02 | Re: pg_upgrade & tablespaces |
| Previous Message | Bruce Momjian | 2013-12-19 21:24:25 | Re: pg_upgrade & tablespaces |