pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tomas Szepe <szepe@pinerecords.com>
To: Stephan Szabo <sszabo@megazone23.bigpanda.com>
Cc: pgsql-bugs@postgresql.org
Subject: Re: db growing out of proportion
Date: Fri, 30 May 2003 09:24:42 +0200
Message-ID: <20030530072442.GD14159@louise.pinerecords.com> (raw)
In-Reply-To: <20030529103316.K60582-100000@megazone23.bigpanda.com>
References: <20030529163239.GA11101@louise.pinerecords.com>
	<20030529103316.K60582-100000@megazone23.bigpanda.com>

> [sszabo@megazone23.bigpanda.com]
> 
> > Trouble is, as the rows in the tables get deleted/inserted/updated
> > (the frequency being a couple thousand rows per minute), the database
> > is growing out of proportion in size.  After about a week, I have
> > to redump the db by hand so as to get query times back to sensible
> > figures.  A transaction that takes ~50 seconds before the redump will
> > then complete in under 5 seconds (the corresponding data/base/ dir having
> > shrunk from ~2 GB to ~0.6GB).
> >
> > A nightly VACCUM ANALYZE is no use.
> >
> > A VACUUM FULL is no use.
> >
> > A VACUUM FULL followed by REINDEX is no use.
> 
> Is the space being taken up by stats_min, this index, some other object?

             relname             | relkind | relpages |  reltuples  
---------------------------------+---------+----------+-------------
 stats_hr                        | r       |    61221 | 3.01881e+06
 stats_hr_pkey                   | i       |    26414 | 3.02239e+06
 stats_min_pkey                  | i       |    20849 |      953635
 stats_hr_start                  | i       |    17218 | 3.02142e+06
 stats_min_start                 | i       |    15284 |      949788
 stats_min                       | r       |    10885 |      948792
 authinfo_pkey                   | i       |     1630 |        1342
 authinfo                        | r       |     1004 |        1342
 contract_ips                    | r       |      865 |         565
 contract_ips_pkey               | i       |      605 |         565

> What does VACUUM FULL VERBOSE stats_min; give you?

Sorry, I can't run a VACUUM FULL at this time.
We're in production use.

-- 
Tomas Szepe <szepe@pinerecords.com>



view thread (15+ messages)  latest in thread

Message-ID: <20030530072442.GD14159@louise.pinerecords.com>
Permalink:  ../20030530072442.GD14159@louise.pinerecords.com/
Also on:    postgresql.org/message-id/20030530072442.GD14159@louise.pinerecords.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: szepe@pinerecords.com, sszabo@megazone23.bigpanda.com, pgsql-bugs@postgresql.org
  Subject: Re: db growing out of proportion
  In-Reply-To: <20030530072442.GD14159@louise.pinerecords.com>
  References: <20030529163239.GA11101@louise.pinerecords.com> <20030529103316.K60582-100000@megazone23.bigpanda.com> <20030530072442.GD14159@louise.pinerecords.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