Date: Fri, 21 Nov 2008 18:57:50 +0100
To: Andrus <kobruleht2@hot.ee>, "Richard Huxton" <dev@archonet.com>
Subject: Re: Hash join on int takes 8..114 seconds
From: PFC <lists@peufeu.com>
Cc: pgsql-performance@postgresql.org
Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8
MIME-Version: 1.0
References: <gg1sv3$27fr$1@news.hub.org> <49253FE1.3070706@archonet.com>
	<0205611B528C4C2CBA99AFC64E57D6E8@andrusnotebook>
	<op.ukw669uvcigqcu@soyouz>
	<75A918DFCF25470FAF96B3FE3D25A38B@andrusnotebook>
	<4926E2B2.9050202@archonet.com>
	<8A78204AA6D44C04B053E6412B244E13@andrusnotebook>
Content-Transfer-Encoding: 7bit
Message-ID: <op.ukzdioivcigqcu@soyouz>
In-Reply-To: <8A78204AA6D44C04B053E6412B244E13@andrusnotebook>
User-Agent: Opera Mail/9.62 (Linux)


> How to vacuum full pg_shdepend automatically so that other users can  
> work at same time ?

	Your table is horribly bloated.
	You must use VACUUM FULL + REINDEX (as superuser) on it, however  
unfortunately, it is blocking.
	Therefore, you should wait for sunday night to do this, when noone will  
notice.
	Meanwhile, you can always VACUUM it (as superuser) and REINDEX it.
	And while you're at it, VACUUM FULL + reindex the entire database.

	To avoid such annoyances in the future, you should ensure that autovacuum  
runs properly ; you should investigate this. If you use a cron'ed VACUUM  
that does not run as superuser, then it will not be able to VACUUM the  
system catalogs, and the problem will come back.