Skip site navigation (1) Skip section navigation (2)

Re: BUG #5185: postgres error "invalid page header in block xx of relation "pg_proc_proname_args_nsp_index"

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Siwat Siwarborvorn <pg-support(at)xsidekick(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5185: postgres error "invalid page header in block xx of relation "pg_proc_proname_args_nsp_index"
Date: 2009-11-13 10:41:33
Message-ID: 4AFD37DD.3000103@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Siwat Siwarborvorn wrote:
> - postgresql 8.3.1 compile with options

Although there isn't anything that might explain this issue, you should
upgrade to the latest 8.3 minor release.

> 6) Every time we fixe by reindex pg_proc_proname_args_nsp_index. 

Did you keep a copy of the data files? What do the corrupt pages look
like? Are they empty, perhaps, or filled with garbage, or random bit
flips or what?

That index shouldn't be very big, so you could just copy the
corresponding file from the data directory, gzip it and send it by
email, so that others can take a look. Might want to check it a hex
editor first to make sure there isn't anything sensitive, though. Or you
can send it off-list if you prefer.

Use "SELECT relfilenode FROM pg_class WHERE
relname='pg_proc_proname_args_nsp_index'" to find out the filename in
the data directory.

-- 
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com

In response to

Responses

pgsql-bugs by date

Next:From: Teodor SigaevDate: 2009-11-13 11:18:32
Subject: Re: BUG #5183: Wrong select results using multicolumn gin indexes
Previous:From: Teodor SigaevDate: 2009-11-13 09:56:50
Subject: Re: BUG #5183: Wrong select results using multicolumn gin indexes

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group