From: Gábor Farkas <gabor@nekomancer.net>
To: Heikki Linnakangas <heikki@enterprisedb.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: select count(*) performance (vacuum did not help)
Date: Mon, 24 Sep 2007 17:04:39 +0200
Message-ID: <46F7D207.3000901@nekomancer.net> (raw)
In-Reply-To: <46F7C9F1.1080805@enterprisedb.com>
References: <46F7C494.1050604@nekomancer.net>
<46F7C9F1.1080805@enterprisedb.com>
Heikki Linnakangas wrote:
> Gábor Farkas wrote:
>> - but in the past, the cron-job was not in place, so the table's size
>> grew to around 800000 entries (in around 80 days)
>
> That bloated your table, so that there's still a lot of empty pages in
> it. VACUUM FULL should bring it back to a reasonable size. Regular
> normal non-FULL VACUUMs should keep it in shape after that.
>
hmm... can a full-vacuum be performed while the database is still "live"
(i mean serving requests)?
will the db still be able to respond to queries?
or in a different way:
if i do a full vacuum to that table only, will the database still serve
data from the other tables at a normal speed?
thanks,
gabor
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-performance@postgresql.org
Cc: gabor@nekomancer.net, heikki@enterprisedb.com
Subject: Re: select count(*) performance (vacuum did not help)
In-Reply-To: <46F7D207.3000901@nekomancer.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