From: | Clodoaldo <clodoaldo(dot)pinto(dot)neto(at)gmail(dot)com> |
---|---|
To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com> |
Cc: | "PostgreSQL - General ML" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Reindex does not finish 8.2.6 |
Date: | 2008-03-13 23:49:57 |
Message-ID: | a595de7a0803131649g1c460bbboc09830ddf794ef08@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
> If it doesn't, then my guess is that it's
> time to see what the hanging process is doing -- try an strace on it, or
> attaching it with gdb and getting a backtrace. (I hope your binaries
> have debug symbols).
Will try it.
Regards, Clodoaldo Pinto Neto
From | Date | Subject | |
---|---|---|---|
Next Message | Sushant Sinha | 2008-03-13 23:56:07 | tsearch2 word separators |
Previous Message | Andrej Ricnik-Bay | 2008-03-13 23:40:45 | Re: postgre vs MySQL |