Re: Re: [GENERAL] cannot vacuum a database !

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: poange(at)technologist(dot)com
Cc: The Hermit Hacker <scrappy(at)hub(dot)org>, pgsql-general(at)postgresql(dot)org, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Re: [GENERAL] cannot vacuum a database !
Date: 2000-08-29 22:32:31
Message-ID: 13725.967588351@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-general

It sounds to me like your index on pg_proc(prosrc) is corrupted, which
unfortunately is pretty easy to do in 6.5 and before --- there weren't
any defenses against overlength index entries, which meant a large
function definition could break it.

Fortunately that index isn't actually used for much of anything (in fact
we took it out of 7.0). So you should be able to limp along until you
can schedule a dump/reload, preferably together with an update to 7.0.
Just don't vacuum pg_proc meanwhile. You can vacuum individual user
tables if you need to, but don't do a system-wide vacuum.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message pgsql-bugs 2000-08-29 23:02:53 table aliases with updates
Previous Message pgsql-bugs 2000-08-29 19:06:51 initdb -t trashes the entire database system

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2000-08-29 22:45:30 Re: 7.1 Release Date
Previous Message Mitch Vincent 2000-08-29 22:01:20 Weighted Searches