| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Gionatan Danti <g(dot)danti(at)assyoma(dot)it>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Recover from corrupted database due to failing disk |
| Date: | 2016-11-02 23:23:03 |
| Message-ID: | 2bbf596e-c6ec-5ec4-25ed-af832b6907c1@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/2/16 6:21 PM, Jim Nasby wrote:
> I wouldn't trust the existing cluster that far. Since it sounds like you
> have no better options, you could use zero_damaged_pages to allow a
> pg_dumpall to complete, but you're going to end up with missing data. So
> what I'd suggest would be:
>
> stop Postgres
> make a copy of the cluster
> start with zero_damaged_pages
> pg_dumpall
> stop and remove the cluster (make sure you've got that backup)
> create a new cluster and load the dump
Oh, and while you're at it, upgrade to a version that's supported. 8.1
has been out of support for 5+ years.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2016-11-03 01:08:14 | Re: Replication (BDR) problem: won't catch up after connection timeout |
| Previous Message | Jim Nasby | 2016-11-02 23:21:45 | Re: Recover from corrupted database due to failing disk |