Re: select count(*) performance (vacuum did not help)

From: Gábor Farkas <gabor(at)nekomancer(dot)net>
To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: select count(*) performance (vacuum did not help)
Date: 2007-09-24 15:04:39
Message-ID: 46F7D207.3000901@nekomancer.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Heikki Linnakangas 2007-09-24 15:07:51 Re: select count(*) performance (vacuum did not help)
Previous Message Heikki Linnakangas 2007-09-24 14:30:09 Re: select count(*) performance (vacuum did not help)