From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Clodoaldo <clodoaldo(dot)pinto(dot)neto(at)gmail(dot)com> |
Cc: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "PostgreSQL - General ML" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Reindex does not finish 8.2.6 |
Date: | 2008-03-14 05:55:07 |
Message-ID: | dcc563d10803132255m69adfaa0sc15cf0bd808ccf95@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Mar 13, 2008 at 5:49 PM, Clodoaldo
<clodoaldo(dot)pinto(dot)neto(at)gmail(dot)com> wrote:
> 2008/3/13, Alvaro Herrera <alvherre(at)commandprompt(dot)com>:
> > Clodoaldo escribió:
> >
> > > 2008/3/13, Alvaro Herrera <alvherre(at)commandprompt(dot)com>:
> > > > Clodoaldo escribió:
> > > >
> > > >
> > > > > Now what is happening is that reindex does not finish even with a
> > > > > small 6,500 rows table and after a reboot. In top there is no CPU or
> > > > > memory usage by postmaster and vmstat shows no disk activity.
> > > >
> > > > Hmm, are you vacuuming the system catalogs appropriately?
> > >
> > > If a simple vacuum in instead of a vacuum full is appropriate then yes
> > > the db is vacuumed every three hours after each bulk insert/delete.
> >
> >
> > As superuser? Take a look at whether relations are skipped during
> > vacuum.
>
> Now I vacuumed with superuser.
>
>
> > Try vacuuming pg_class, pg_index, pg_attribute manually and see if that
> > makes the problem go away.
>
> It does not go away.
Could this be a problem with a bloated table that needs a vacuum full?
I'd try that.
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2008-03-14 06:14:48 | Re: Can't rename an existnig DB because it doesn't exist??? |
Previous Message | J Ottery | 2008-03-14 04:48:11 | Using MicroOLAP DAC to connect to Database - Problem with Grid |