Re: postgres bogged down beyond tolerance

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tena Sakai" <tsakai(at)gallo(dot)ucsf(dot)edu>, "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: postgres bogged down beyond tolerance
Date: 2007-11-14 21:33:09
Message-ID: 473B1535.EE98.0025.0@wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

>>> 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?

-Kevin

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Marlowe 2007-11-14 21:46:00 Re: postgres bogged down beyond tolerance
Previous Message Scott Marlowe 2007-11-14 21:20:53 Re: cached memory