Hi Scott, Kevin, Alvaro, and everybody else:
Many thanks for your help and advices. After vacuuming
and reindexing all tables, my nightly run zipped right
through at amazing speed.
From: Scott Marlowe [mailto:scott(dot)marlowe(at)gmail(dot)com]
Sent: Wed 11/14/2007 1:46 PM
To: Kevin Grittner
Cc: Tena Sakai; pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] postgres bogged down beyond tolerance
On Nov 14, 2007 3:33 PM, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> >>> On Wed, Nov 14, 2007 at 3:16 PM, in message
> <dcc563d10711141316u53338170l5d31d7723c8dc30b(at)mail(dot)gmail(dot)com>, "Scott Marlowe"
> <scott(dot)marlowe(at)gmail(dot)com> wrote:
> > On Nov 14, 2007 2:26 PM, Tena Sakai <tsakai(at)gallo(dot)ucsf(dot)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.
In response to
pgsql-admin by date
|Next:||From: Tom Lane||Date: 2007-11-15 05:37:27|
|Subject: Re: Error: duplicate key violates unique constraint - "pg_toast_3270368541_index |
|Previous:||From: scrappy||Date: 2007-11-15 04:12:33|
|Subject: Upgrading a database with pg_dumpall / psql ...|