pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <scott.marlowe@gmail.com>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Tena Sakai <tsakai@gallo.ucsf.edu>
Cc: pgsql-admin@postgresql.org
Subject: Re: postgres bogged down beyond tolerance
Date: Wed, 14 Nov 2007 15:46:00 -0600
Message-ID: <dcc563d10711141346u2037c75dnbb389ef08a8622b9@mail.gmail.com> (raw)
In-Reply-To: <473B1535.EE98.0025.0@wicourts.gov>
References: <FE44E0D7EAD2ED4BB2165071DB8E328C03062D9A@egcrc-ex01.egcrc.org>
	<dcc563d10711141147x4c32142es449f20d13b8d05a7@mail.gmail.com>
	<FE44E0D7EAD2ED4BB2165071DB8E328C03062D9D@egcrc-ex01.egcrc.org>
	<dcc563d10711141316u53338170l5d31d7723c8dc30b@mail.gmail.com>
	<473B1535.EE98.0025.0@wicourts.gov>

On Nov 14, 2007 3:33 PM, Kevin Grittner <Kevin.Grittner@wicourts.gov> wrote:
> >>> On Wed, Nov 14, 2007 at  3:16 PM, in message
> <dcc563d10711141316u53338170l5d31d7723c8dc30b@mail.gmail.com>, "Scott Marlowe"
> <scott.marlowe@gmail.com> wrote:
>
> > On Nov 14, 2007 2:26 PM, Tena Sakai <tsakai@gallo.ucsf.edu> wrote:
> >>  INFO:  vacuuming "public.allele"
> >>  INFO:  "allele": found 2518282 removable, 1257262 nonremovable row versions
> >> in 31511 pages
>
> >>  Total free space (including removable row versions) is 161940948 bytes.
>
> > It looks to me like your tables were bloated.  After running vacuum
> > full your cron should run faster now.
>
> Isn't it usually a good idea to REINDEX after using VACUUM FULL to
> recover from this level of bloat?

Depends on your indexes.  These didn't look bloated to me, but that
wasn't the whole output of vacuum full either.  Yes, reindex is a good
idea after a vacuum full though.



view thread (8+ messages)  latest in thread

Message-ID: <dcc563d10711141346u2037c75dnbb389ef08a8622b9@mail.gmail.com>
Permalink:  ../dcc563d10711141346u2037c75dnbb389ef08a8622b9@mail.gmail.com/
Also on:    postgresql.org/message-id/dcc563d10711141346u2037c75dnbb389ef08a8622b9@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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: scott.marlowe@gmail.com, Kevin.Grittner@wicourts.gov, tsakai@gallo.ucsf.edu
  Subject: Re: postgres bogged down beyond tolerance
  In-Reply-To: <dcc563d10711141346u2037c75dnbb389ef08a8622b9@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