From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Aris Samad-Yahaya <aris(at)quickschools(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: CREATE TABLE slowing down significantly over time |
Date: | 2009-11-09 12:22:02 |
Message-ID: | 603c8f070911090422t52412697hf19b222a033f729@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Sat, Nov 7, 2009 at 11:58 PM, Aris Samad-Yahaya
<aris(at)quickschools(dot)com> wrote:
> We vacuum analyze nightly, and vacuum normally ad-hoc (but we're going to
> schedule this weekly moving forward).
>
> Interesting pointer about system catalog bloat. I tried to vacuum full the
> system catalog tables (pg_*), and the performance for creating a single
> table manually improved dramatically (back to what it used to be), but as
> soon as I created the next schema, the performance went back down to the
> same level.
>
> So there's a clue there somewhere. Next I will try to vacuum full the entire
> database.
You should really enable autovacuum. You'll probably have to VACUUM
FULL and REINDEX to clean everything up, but after that autovacuum
should be MUCH more effective than a nightly vacuum run. If you're
running some ancient Pg version where autovacuum is not enabled by
default, you should also consider upgrading. There are a lot of
goodies (including performance enhancements) in newer versions.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Laszlo Nagy | 2009-11-09 12:58:47 | random_page_cost for tablespace |
Previous Message | Grzegorz Jaśkiewicz | 2009-11-09 08:40:30 | Re: CREATE TABLE slowing down significantly over time |