From: | Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: page is uninitialized --- fixing |
Date: | 2008-03-27 13:09:45 |
Message-ID: | 1206623385.26138.39.camel@bnicholson-desktop |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 2008-03-26 at 15:31 -0400, Tom Lane wrote:
> Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info> writes:
> > We just took a test database down (PG 8.1.11) fairly hard (pulled a SAN
> It could be that but not necessarily. These could be pages that were
> allocated to put new tuples into, but the crash happened before the
> inserting transaction committed (and, in fact, before any of the
> associated WAL entries had made their way to disk -- else the empty
> pages would've been initialized during WAL replay).
>
> It would be easier to believe that if the uninitialized pages were all
> contiguous though. Do you know that this table was under heavy insert
> load at the time?
It was. This table is an insert only log table that was being heavily
was being heavily written to at the time of the crash.
Brad.
From | Date | Subject | |
---|---|---|---|
Next Message | Geoffrey | 2008-03-27 13:27:30 | Re: Survey: renaming/removing script binaries (createdb, createuser...) |
Previous Message | Albe Laurenz | 2008-03-27 13:07:19 | Re: returned value from SQL statement |