Thread: Panic: Page Add Item: Corrupted page pointers

Hi,

 

I'm getting this error when try to create a table in Postgresql 7.3, windows2000:

 

Panic: Page Add Item: Corrupted page pointers: lower=24258, upper=39318, special=65421

 

LOG: statement = create table data(key unique, status text, info text)

LOG: pg_recvby : unexpected EOF on client connection

LOG: server process <pid 13847> was terminated by signal 6

LOG: all server processes terminated; reinitializing shared memory and semaphores

.....

 

Thank you

 

 

 

---

Yahoo! for Good
Watch the Hurricane Katrina Shelter From The Storm concert

On Sun, Sep 11, 2005 at 02:20:01PM -0700, The One wrote:
> Actually, I'm getting this error everytime I try to create a table.
>  
> Can someone please help?

Where did you get that version of PostgreSQL?  Is it the Cygwin version?
AFAIK it's labelled as "not robust enough for production".

> The One <i51359@yahoo.com> wrote:
> Hi,
>  
> I'm getting this error when try to create a table in Postgresql 7.3, windows2000:
>  
> Panic: Page Add Item: Corrupted page pointers: lower=24258, upper=39318, special=65421

Clearly the page is corrupt.  The fact that you are using an unsupported
version does not help you get a lot of support ...  Also, note that this
is quite off-topic for pgsql-sql.

-- 
Alvaro Herrera -- Valdivia, Chile         Architect, www.EnterpriseDB.com
Este mail se entrega garantizadamente 100% libre de sarcasmo.

The One <i51359@yahoo.com> writes:
> I'm getting this error when try to create a table in Postgresql 7.3, windows2000:
> Panic: Page Add Item: Corrupted page pointers: lower=24258, upper=39318, special=65421

Apparently you've got at least one corrupt page in at least one system
table.  I'd recommend pg_dump'ing as much as you can and then recreate
the database.

If pg_dump doesn't work you could try turning on zero_damaged_pages,
and praying that most of what you need is on undamaged pages.  It's
quite possible though that that will hose the DB completely, so don't do
it till you've exhausted the possibilities for pg_dump without it.

Consider updating to a more recent PG release while you are
recovering...
        regards, tom lane