From: Greg Williamson <gwilliamson39@yahoo.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: autovacuum with lots of open file references to deleted files
Date: Sun, 4 Nov 2012 17:40:22 -0800 (PST)
Message-ID: <1352079622.31433.YahooMailNeo@web125901.mail.ne1.yahoo.com> (raw)
In-Reply-To: <27617.1352076455@sss.pgh.pa.us>
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>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: gwilliamson39@yahoo.com
Subject: Re: autovacuum with lots of open file references to deleted files
In-Reply-To: <1352079622.31433.YahooMailNeo@web125901.mail.ne1.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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