pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
problem with pg_statistic_relid_att_index 2+ messages / 2 participants [nested] [flat]
* problem with pg_statistic_relid_att_index @ 2008-03-10 12:57 Tony Da Silva <tony@altonet.co.za> 2008-03-10 14:49 ` Re: problem with pg_statistic_relid_att_index Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 1 reply; 2+ messages in thread From: Tony Da Silva @ 2008-03-10 12:57 UTC (permalink / raw) To: pgsql-admin Hi, I seem to have a problem on one of my databases, When I log into pgsql I see this: ERROR: Invalid page header in block 3 of pg_statistic_relid_att_index Welcome to psql 7.3.4, the PostgreSQL interactive terminal. When I try to run any command (eg vacuum) I get this message: dbname=> vacuum full; ERROR: current transaction is aborted, queries ignored until end of transaction block reindex also does not work: dbname=> reindex index pg_statistic_relid_att_index; ERROR: current transaction is aborted, queries ignored until end of transaction block Please can somebody help if you know how to fix this. Thx Tony ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: problem with pg_statistic_relid_att_index 2008-03-10 12:57 problem with pg_statistic_relid_att_index Tony Da Silva <tony@altonet.co.za> @ 2008-03-10 14:49 ` Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 2+ messages in thread From: Tom Lane @ 2008-03-10 14:49 UTC (permalink / raw) To: tony@altonet.co.za; +Cc: pgsql-admin "Tony Da Silva" <tony@altonet.co.za> writes: > When I log into pgsql I see this: > ERROR: Invalid page header in block 3 of pg_statistic_relid_att_index I can't think of any reason that a simple connection attempt would be trying to read pg_statistic. Perhaps you have some nontrivial query in your ~/.psqlrc? If so try taking that out. If that doesn't work you might have to resort to setting zero_damaged_pages in postgresql.conf, but that's a pretty dangerous tool --- it might zap pages you weren't expecting it to. Don't keep it on any longer than you absolutely have to. Once you do get into the DB you should be able to just REINDEX pg_statistic to fix the problem. (In 7.3 you might have to use a standalone backend for that, I don't recall for sure.) > Welcome to psql 7.3.4, the PostgreSQL interactive terminal. Egad. You do know that 7.3 was up to 7.3.21 before we obsoleted it? If your DB is unrecoverable because of some data-eating bug that was fixed in the past four-plus years, you're not going to get a lot of sympathy. regards, tom lane ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2008-03-10 14:49 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2008-03-10 12:57 problem with pg_statistic_relid_att_index Tony Da Silva <tony@altonet.co.za> 2008-03-10 14:49 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox