Re: PITR Backups

From: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Dan Gorman" <dgorman(at)hi5(dot)com>, "Koichi Suzuki" <suzuki(dot)koichi(at)oss(dot)ntt(dot)co(dot)jp>, "Toru SHIMOGAKI" <shimogaki(dot)toru(at)oss(dot)ntt(dot)co(dot)jp>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: PITR Backups
Date: 2007-06-25 16:56:06
Message-ID: 1182790567.9276.609.camel@silverbirch.site
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Mon, 2007-06-25 at 12:34 -0400, Tom Lane wrote:
> Dan Gorman <dgorman(at)hi5(dot)com> writes:
> > Jun 21 00:39:43 sfmedstorageha001 postgres[3506]: [9-1] 2007-06-21
> > 00:39:43 PDTLOG: redo done at 71/99870670

This is mid-way through an xlog file.

> > Jun 21 00:39:43 sfmedstorageha001 postgres[3506]: [10-1] 2007-06-21
> > 00:39:43 PDTWARNING: page 28905 of relation 1663/16384/76718 was
> > uninitialized
> > ... lots of these ...
> > Jun 21 00:39:43 sfmedstorageha001 postgres[3506]: [40-1] 2007-06-21
> > 00:39:43 PDTPANIC: WAL contains references to invalid pages
>
> (BTW, you'll find putting a space at the end of log_line_prefix
> does wonders for log readability.)
>
> Reformatting and sorting, we have
>
> WARNING: page 28900 of relation 1663/16384/76718 was uninitialized
> WARNING: page 28902 of relation 1663/16384/76718 was uninitialized

> WARNING: page 26706 of relation 1663/16384/76719 was uninitialized
> WARNING: page 26708 of relation 1663/16384/76719 was uninitialized

Those two are interesting because we appear to have two valid pages in
the middle of some uninitialized ones. That implies were not looking at
an unapplied truncation.

--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Dan Gorman 2007-06-25 17:04:48 Re: PITR Backups
Previous Message Tom Lane 2007-06-25 16:34:18 Re: PITR Backups