From: | Bill Moran <wmoran(at)collaborativefusion(dot)com> |
---|---|
To: | \"Gábor Farkas\" <gabor(at)nekomancer(dot)net> |
Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: select count(*) performance (vacuum did not help) |
Date: | 2007-09-24 15:29:07 |
Message-ID: | 20070924112907.cbede7e6.wmoran@collaborativefusion.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
In response to "Gábor Farkas" <gabor(at)nekomancer(dot)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(at)collaborativefusion(dot)com
Phone: 412-422-3463x4023
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Staubo | 2007-09-24 15:29:48 | Re: TEXT or LONGTEXT? |
Previous Message | Fabiola Fernández | 2007-09-24 15:21:25 | TEXT or LONGTEXT? |