2008/3/14, Scott Marlowe <scott.marlowe@gmail.com>:
> On Thu, Mar 13, 2008 at 5:49 PM, Clodoaldo
> <clodoaldo.pinto.neto@gmail.com> wrote:
> > 2008/3/13, Alvaro Herrera <alvherre@commandprompt.com>:
> > > Clodoaldo escribió:
> > >
> > > > 2008/3/13, Alvaro Herrera <alvherre@commandprompt.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.
Vacuum full also hangs.
Regards, Clodoaldo Pinto Neto
