DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:Cc:In-Reply-To:MIME-Version:Content-Type;
	b=Vv6m9ay2t1CYHqimQJ7VlPMzLg8Ew70kLdl8+GOW7Zfn721MuRDy8IVLeyhCc6iwt0MIps5khbtf6nDzplqx2t2PcUIhoWZzv37eUSy4h3DDOOFEkwe/UyCpuYHtBesodHRWvSlSC6sbSDPDhiH3JEYfDECuiB4YaMQetOcziPI=;
References: <B9BEA448-978F-4A14-A088-3FD82214FFAC@pvv.ntnu.no>
	<7015.1350260875@sss.pgh.pa.us>
	<347905F6-B93E-4259-A8A9-28DBAC51D014@pvv.ntnu.no>
	<27617.1352076455@sss.pgh.pa.us>
Message-ID: <1352079622.31433.YahooMailNeo@web125901.mail.ne1.yahoo.com>
Date: Sun, 4 Nov 2012 17:40:22 -0800 (PST)
From: Greg Williamson <gwilliamson39@yahoo.com>
Reply-To: Greg Williamson <gwilliamson39@yahoo.com>
Subject: Re: autovacuum with lots of open file references to deleted files
Cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
In-Reply-To: <27617.1352076455@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Tom --


<...>
>>  A cron job dropdb one of the databases and createdb it and then pg_restore. 
> Roughly 80GB dump. 
> 
> So far, my guess is that this is fixed by commits a1f064fc2 + d7598aeea.
> 
>>  Out production PostgreSQL running a 9.1 variant does not have this problem. 
> It does not have the nightly dropdb/createdb/pg_restore, but otherwise similar 
> usage patterins. It is also configured to use more memory.
> 
> 9.1 has the same bug (and the same patches), but I think that the aspect
> you're running into is specific to DROP DATABASE scenarios.
> 

Is there any idea of when this will be released ?

Thanks,

Greg W.