| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: page is uninitialized --- fixing |
| Date: | 2009-06-09 18:22:02 |
| Message-ID: | 1244571722.15799.345.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2009-06-09 at 13:54 -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> > A couple of people in recent years have had a problem with "page X is
> > uninitialised -- fixing" messages.
>
> > I have a case now with 569357 consecutive pages that required fixing in
> > pg_attribute. We looked at pages by hand and they really are
> > uninitialised, but otherwise what we would expect for size, name etc..
>
> What PG version?
PG 8.3.7 on CentOS. Other client mentioned is 8.3 on SuSE.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gurjeet Singh | 2009-06-09 18:23:44 | Re: Not quite a security hole in internal_in |
| Previous Message | Tom Lane | 2009-06-09 18:20:08 | Re: information_schema.columns changes needed for OLEDB |