| From: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
|---|---|
| To: | "Eric B(dot) Ridge" <ebr(at)tcdi(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Corruption on production system |
| Date: | 2005-04-26 01:42:52 |
| Message-ID: | 20050426014252.GA31204@dcc.uchile.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Apr 25, 2005 at 08:24:03PM -0400, Eric B. Ridge wrote:
> Is page header corruption a known issue with 7.3.6 and should I
> upgrade to 7.3.9 at the same time that I'm restoring this table from
> backup?
Well, you can get a page header corruption on any release as long as you
have faulty hardware ... RAM randomly dropping bits is not unheard of.
Have you run memtest?
If you don't mind losing that page of data, you could turn on
zero_damaged_pages on postgresql.conf. If you do, you could try
pg_filedump (to be found somewhere on sources.redhat.com/rhdb IIRC) to
examine the damaged page more closely.
--
Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>)
"Vivir y dejar de vivir son soluciones imaginarias.
La existencia está en otra parte" (Andre Breton)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Eric B. Ridge | 2005-04-26 01:49:43 | Re: Corruption on production system |
| Previous Message | Christopher Kings-Lynne | 2005-04-26 01:40:19 | Re: OpenRPT (was Re: [ANNOUNCE] == PostgreSQL Weekly |