From: Matthew T. O'Connor <matthew@zeut.net>
To: Eamonn Kent <ekent@xsigo.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Vacuum issues..
Date: Mon, 21 Aug 2006 19:20:49 -0400
Message-ID: <44EA3FD1.4020505@zeut.net> (raw)
In-Reply-To: <9146E3EBBFBCC94D95F95A1C4065348A837AB0@exch01.xsigo.com>
References: <9146E3EBBFBCC94D95F95A1C4065348A837AB0@exch01.xsigo.com>
Eamonn Kent wrote:
> I am using PostgreSQL 8.1.4 for an embedded application. For some
> reason, vacuum is not able to identify rows that are candidates for
> removal (i.e., mark space as available).
[snip]
>
> If I shutdown our application and run a vacuum full, the space is
> recovered and the database size goes down to 150M.
The most common answer to this is that your application is leaving open
transactions just sitting there. VACUUM can't remove tuples that may
still need to be visible to a transaction that's been open for days.
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: matthew@zeut.net, ekent@xsigo.com
Subject: Re: Vacuum issues..
In-Reply-To: <44EA3FD1.4020505@zeut.net>
* 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