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

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 (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-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

pgsql-bugs by date

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

pgsql-general by date

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

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