| From: | Clodoaldo <clodoaldo(dot)pinto(dot)neto(at)gmail(dot)com> |
|---|---|
| To: | "Pavan Deolasee" <pavan(dot)deolasee(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 10:25:41 |
| Message-ID: | a595de7a0803140325q2b5d431o166c4c3922b27a87@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2008/3/14, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>:
> On Fri, Mar 14, 2008 at 5:19 AM, Clodoaldo
>
> <clodoaldo(dot)pinto(dot)neto(at)gmail(dot)com> wrote:
>
> >
>
> > > Try vacuuming pg_class, pg_index, pg_attribute manually and see if that
> > > makes the problem go away.
> >
> > It does not go away.
> >
>
>
> Can it be a case where some other open transaction is holding a lock
> on the table ? Note that REINDEX would block even some other transaction
> is inserting/deleting/updating the table.
Postgresql was restarted twice, but yes, it is as if the crash left
some kind of permanent lock somewhere.
Regards, Clodoaldo Pinto Neto
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Leif B. Kristensen | 2008-03-14 10:50:31 | Re: postgre vs MySQL |
| Previous Message | Clodoaldo | 2008-03-14 10:21:05 | Re: Reindex does not finish 8.2.6 |