From: Bill Moran <wmoran@collaborativefusion.com>
To: \"Gábor Farkas\" <gabor@nekomancer.net>
Cc: Heikki Linnakangas <heikki@enterprisedb.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: select count(*) performance (vacuum did not help)
Date: Mon, 24 Sep 2007 11:29:07 -0400
Message-ID: <20070924112907.cbede7e6.wmoran@collaborativefusion.com> (raw)
In-Reply-To: <46F7D453.4050908@nekomancer.net>
References: <46F7C494.1050604@nekomancer.net>
<46F7C9F1.1080805@enterprisedb.com>
<46F7D207.3000901@nekomancer.net>
<46F7D2C7.70105@enterprisedb.com>
<46F7D453.4050908@nekomancer.net>
In response to "Gábor Farkas" <gabor@nekomancer.net>:
> Heikki Linnakangas wrote:
> > Gábor Farkas wrote:
> >>
> >> if i do a full vacuum to that table only, will the database still serve
> >> data from the other tables at a normal speed?
> >
> > Yes. The extra I/O load vacuum full generates while it's running might
> > disrupt other activity, though.
> >
>
> i see.
>
> will i achieve the same thing by simply dropping that table and
> re-creating it?
Yes. Once you've done so, keep up the vacuum schedule you've already
established. You may want to (as has already been suggested) explicitly
vacuum this table after large delete operations as well.
--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/
wmoran@collaborativefusion.com
Phone: 412-422-3463x4023
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: wmoran@collaborativefusion.com, gabor@nekomancer.net, heikki@enterprisedb.com
Subject: Re: select count(*) performance (vacuum did not help)
In-Reply-To: <20070924112907.cbede7e6.wmoran@collaborativefusion.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