Re: PostgreSQL slow after VACUUM - Mailing list pgsql-general

From Greg Stark
Subject Re: PostgreSQL slow after VACUUM
Date
Msg-id 87pt20x4xm.fsf@stark.xeocode.com
Whole thread Raw
In response to Re: PostgreSQL slow after VACUUM  (Arjen van der Meijden <acmmailing@vulcanus.its.tudelft.nl>)
List pgsql-general
Arjen van der Meijden <acmmailing@vulcanus.its.tudelft.nl> writes:

> My suggestion is to VACUUM (FULL) the table after you've deleted the data.
> Then fill up the table and do a ANALYZE when you're done filling it.

For now you might be able to improve matters by doing an ANALYZE even while
it's busy doing the import. Depending on how the import is coded it may or may
not have an immediate effect.

VACUUM and ANALYZE (and VACUUM ANALYZE) are fairly quick and don't block
access to the tables, though they can slow it down somewhat. You probably want
to be running them frequently so you don't have to resort to VACUUM FULL.

--
greg

pgsql-general by date:

Previous
From: Arjen van der Meijden
Date:
Subject: Re: PostgreSQL slow after VACUUM
Next
From: "Ramesh Patel"
Date:
Subject: PostgreSQL Config.