From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tore Halset <halset@pvv.ntnu.no>
Cc: pgsql-admin@postgresql.org
Subject: Re: autovacuum with lots of open file references to deleted files
Date: Sun, 14 Oct 2012 20:27:55 -0400
Message-ID: <7015.1350260875@sss.pgh.pa.us> (raw)
In-Reply-To: <B9BEA448-978F-4A14-A088-3FD82214FFAC@pvv.ntnu.no>
References: <B9BEA448-978F-4A14-A088-3FD82214FFAC@pvv.ntnu.no>
Tore Halset <halset@pvv.ntnu.no> writes:
> On this box I drop a 80GB database each night followed by a restore of a similar sized database. It is a restore of our production database to a development server. This box is running 9.2rc1 (sorry).
> du and df reported quite different numbers and lsof show that autovacuum is holding lots of deleted files. After killing the autovacuum daemon, some disk space was restored and the du and df numbers was more equal.
> autovacuum hold roughly 100GB of deleted files. This running PostgreSQL instance has dumped/restored the 80GB database ~20 times.
Hm. I've been able to reproduce some leakage of file descriptors in the
autovac launcher, but it required (a) fairly small shared_buffers and
(b) very heavy update activity on large tables. So I'm not sure that it
would explain the consistent leakage you seem to be seeing. Can you
tell us more about your usage pattern on the development server? What
nondefault settings are you using on it?
regards, tom lane
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: tgl@sss.pgh.pa.us, halset@pvv.ntnu.no
Subject: Re: autovacuum with lots of open file references to deleted files
In-Reply-To: <7015.1350260875@sss.pgh.pa.us>
* 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