From: Robert Haas <robertmhaas@gmail.com>
To: Aris Samad-Yahaya <aris@quickschools.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: CREATE TABLE slowing down significantly over time
Date: Mon, 9 Nov 2009 07:22:02 -0500
Message-ID: <603c8f070911090422t52412697hf19b222a033f729@mail.gmail.com> (raw)
In-Reply-To: <009601ca6030$0e731440$2b593cc0$@com>
References: <008801ca6021$c1cc7630$45656290$@com>
<18869.1257650960@sss.pgh.pa.us>
<009601ca6030$0e731440$2b593cc0$@com>
On Sat, Nov 7, 2009 at 11:58 PM, Aris Samad-Yahaya
<aris@quickschools.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
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: robertmhaas@gmail.com, aris@quickschools.com, tgl@sss.pgh.pa.us
Subject: Re: CREATE TABLE slowing down significantly over time
In-Reply-To: <603c8f070911090422t52412697hf19b222a033f729@mail.gmail.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