From: Tom Lane <tgl@sss.pgh.pa.us>
To: Boguk Maxim <astar@rambler-co.ru>
Cc: 'Gourish Singbal' <gourish@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Some strange issues with VACUUM on one table.
Date: Tue, 20 Dec 2005 09:52:35 -0500
Message-ID: <28966.1135090355@sss.pgh.pa.us> (raw)
In-Reply-To: <291ABF6CBE162F45B006AFF7AB770B8806F8A7C3@office.rambler.stack.net>
References: <291ABF6CBE162F45B006AFF7AB770B8806F8A7C3@office.rambler.stack.net>
Boguk Maxim <astar@rambler-co.ru> writes:
> I trying understand why vacuum analyze do not work at all.
I think either you're not actually applying vacuum analyze at all
(better double-check your daily maintenance script), or you're somehow
managing to apply it at a time when it can't remove old rows because
there's still an open transaction that might be able to see those rows.
The latter theory doesn't really explain continuing table growth over
time, though, unless you've got a transaction that's been sitting open
the entire time.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, astar@rambler-co.ru, gourish@gmail.com
Subject: Re: Some strange issues with VACUUM on one table.
In-Reply-To: <28966.1135090355@sss.pgh.pa.us>
References: <291ABF6CBE162F45B006AFF7AB770B8806F8A7C3@office.rambler.stack.net> <28966.1135090355@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