Skip site navigation (1) Skip section navigation (2)

Re: PITR Backups

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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 17:07:24
Message-ID: 87ps3kt12r.fsf@oxford.xeocode.com (view raw or flat)
Thread:
Lists: pgsql-performance
"Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:

>> 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.

You don't have fsync off do you? That could explain missing pages at the end
of a file like this too. And it would explain how you could have two written
in the midst of others that are missing.

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com


In response to

Responses

pgsql-performance by date

Next:From: Tom LaneDate: 2007-06-25 17:10:45
Subject: Re: PITR Backups
Previous:From: Dan GormanDate: 2007-06-25 17:04:48
Subject: Re: PITR Backups

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group