Re: Error in log file after database crash

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Rob Cowell <rob(dot)cowell(at)transversal(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Error in log file after database crash
Date: 2016-05-10 03:21:28
Message-ID: CAB7nPqTQerHGKA6fjpcac1fsoAjOsFmZb4zS0OkZ8QR9dUxcFQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, May 10, 2016 at 1:11 AM, Rob Cowell <rob(dot)cowell(at)transversal(dot)com> wrote:
> Currently I'm running 9.1.10,

9.1.10 has been released in 2013. You are missing 2 years and a half
worth of various fixes, so you may want to update to 9.1.22 first.

> [2016-05-05 20:09:00 UTC] LOCATION: XLogFlush, xlog.c:2171
> [2016-05-05 20:09:00 UTC] WARNING: 58030: could not write block 0 of pg_tblspc/16395/PG_9.1_201105231/16400/33044487_vm
> [2016-05-05 20:09:00 UTC] DETAIL: Multiple failures --- write error might be permanent.
> [2016-05-05 20:09:00 UTC] LOCATION: AbortBufferIO, bufmgr.c:2799

This looks like corrupted data, but that's hard to tell with this
level of details. Rolling in a logical backup may be the best way to
go forward here.
--
Michael

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Sameer Kumar 2016-05-10 07:20:42 Re: Inserting into a master table with partitions does not return rows affected.
Previous Message D'Arcy J.M. Cain 2016-05-10 02:46:55 Re: Using both ident and password in pg_hba.conf