| From: | Clodoaldo <clodoaldo(dot)pinto(dot)neto(at)gmail(dot)com> | 
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com> | 
| Cc: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>, "PostgreSQL - General ML" <pgsql-general(at)postgresql(dot)org> | 
| Subject: | Re: Reindex does not finish 8.2.6 | 
| Date: | 2008-03-14 13:31:18 | 
| Message-ID: | a595de7a0803140631l38780c1btbc3650c1581ae61e@mail.gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
2008/3/14, Alvaro Herrera <alvherre(at)commandprompt(dot)com>:
> Clodoaldo escribió:
>
>
>  > Postgresql was restarted twice, but yes, it is as if the crash left
>  > some kind of permanent lock somewhere.
>
>
> A prepared transaction perhaps?  SELECT * FROM pg_prepared_xacts;
>
>  A quick look into pg_locks should tell you if it's blocking.
pg_prepared_xacts is empty and pg_locks has 288 rows:
# select locktype, mode, count(*) as total
from pg_locks group by locktype, mode;
   locktype    |       mode       | total
---------------+------------------+-------
 transactionid | ExclusiveLock    |    30
 relation      | RowExclusiveLock |     2
 relation      | AccessShareLock  |   256
(3 rows)
Regards, Clodoaldo Pinto Neto
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2008-03-14 13:50:00 | Re: GRANT giving error on sequence in 7.4.19 | 
| Previous Message | Joshua D. Drake | 2008-03-14 13:30:47 | Re: PG secure for financial applications ... |