Re: Invalid Page Header
От | Christopher A. Goodfellow |
---|---|
Тема | Re: Invalid Page Header |
Дата | |
Msg-id | 000901c643b0$f6441580$060a640a@wks10 обсуждение исходный текст |
Ответ на | Re: Invalid Page Header (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-novice |
Thank You. I set zero_damaged_pages to on using the owner user for the database and did a select count(). The response was fixing. After setting zero_damaged_pages to off, I still received the Invalid Page Header error. I then set zero back to on and did a vacuum on the table. This solved the problem. I did loose one row of data but I expected that. Thank You, Christopher A. Goodfellow Corporate Director Tealuxe, Inc. Phone: 508-520-7887 Fax: 508-528-8999 Tea For All -----Original Message----- From: pgsql-novice-owner@postgresql.org [mailto:pgsql-novice-owner@postgresql.org]On Behalf Of Tom Lane Sent: Thursday, March 09, 2006 2:20 PM To: Christopher A. Goodfellow Cc: 'Michael Fuhr'; 'Pgsql-Novice (E-mail)' Subject: Re: [NOVICE] Invalid Page Header "Christopher A. Goodfellow" <cgoodfellow@tealuxe.com> writes: > I have read quite a bit in the archives and it seems the best way is to > zero_damaged_pages. I did a search for zero_damaged_pages. Is it as simple > as adding zero_damaged_pages to postgresql.conf and restarting the > postmaster? Since zero_damaged_pages is a pretty dangerous thing to have on, I wouldn't recommend turning it on in postgresql.conf. Instead, turn it on within a single session using SET, and then scan the tables that you want to clean up (a VACUUM or SELECT COUNT(*) will do). regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly
В списке pgsql-novice по дате отправления: