pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <scott.marlowe@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: Sat, 7 Nov 2009 22:30:56 -0700
Message-ID: <dcc563d10911072130i6e029e5dg815d4f7909e19383@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 9: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.

If you don't run autovac, it's possible you've managed to bloat your
pg_catalog tables...  Note that we run similar numbers of tables, as
we have 30 tables and about 10 indexes in over 2000 schemas.  We did
the trick Tom posted:
alter function pg_table_is_visible(oid) cost 10;
to get faster tab completion and / or \d performance.



view thread (13+ messages)  latest in thread

Message-ID: <dcc563d10911072130i6e029e5dg815d4f7909e19383@mail.gmail.com>
Permalink:  ../dcc563d10911072130i6e029e5dg815d4f7909e19383@mail.gmail.com/
Also on:    postgresql.org/message-id/dcc563d10911072130i6e029e5dg815d4f7909e19383@mail.gmail.com

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: scott.marlowe@gmail.com, aris@quickschools.com, tgl@sss.pgh.pa.us
  Subject: Re: CREATE TABLE slowing down significantly over time
  In-Reply-To: <dcc563d10911072130i6e029e5dg815d4f7909e19383@mail.gmail.com>
  References: <008801ca6021$c1cc7630$45656290$@com> <18869.1257650960@sss.pgh.pa.us> <009601ca6030$0e731440$2b593cc0$@com> <dcc563d10911072130i6e029e5dg815d4f7909e19383@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