Postgres Pro
Downloads
Home   >   mailing lists

Re: corruption issue after server crash - ERROR: unexpected chunk number 0 - Mailing list pgsql-general

From Mike Broers
Subject Re: corruption issue after server crash - ERROR: unexpected chunk number 0
Date
Msg-id CAB9893hXCLgxyPNZ=qPUimRhiBWR_hborL6p8VbGcTPURxeTUA@mail.gmail.com
Whole thread Raw
In response to Re: corruption issue after server crash - ERROR: unexpected chunk number 0  (Kevin Grittner <kgrittn@ymail.com>)
Responses Re: corruption issue after server crash - ERROR: unexpected chunk number 0
List pgsql-general
Tree view
vacuumb avz, pg_dumpall, and vacuum freeze analyze on the former standby database that received the corruption via replication all came back without errors.  Is the vacuum freeze intended to potentially fix problems or just reveal if other tables may have corruption, Im trying to decide if this needs to be run in production.


On Thu, Nov 21, 2013 at 5:09 PM, Kevin Grittner <kgrittn@ymail.com> wrote:
Mike Broers <mbroers@gmail.com> wrote:

> Is there anything I should look out for with vacuum freeze?

Just check the logs and the vacuum output for errors and warnings.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-general by date:

Previous
From:
Date:
Subject: Re: [GENERAL] Puzzling table scan in a CTE
Next
From: Brian Wong
Date:
Subject: Re: ERROR: out of memory DETAIL: Failed on request of size ???