| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Subject: | Re: Index trouble with 8.3b4 |
| Date: | 2008-01-08 23:21:27 |
| Message-ID: | 19366.1199834487@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> Further poking around shows that the "unrecognized locktag" is because
> lmgr.c:DescribeLockTag was never taught about virtual xids.
That's fixed, thanks for the patch.
> The pid it's waiting on is long since gone but looks like it was probably an
> autovacuum process. I have a vague recollection that you had rigged CREATE
> INDEX CONCURRENTLY to ignore vacuum processes when checking for conflicting
> processes.
I'm still not too clear on the underlying bug though.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-01-08 23:47:47 | Re: Index trouble with 8.3b4 |
| Previous Message | D. Dante Lorenso | 2008-01-08 22:41:09 | WHERE vs ORDER BY vs LIMIT why not using the correct index? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-01-08 23:47:47 | Re: Index trouble with 8.3b4 |
| Previous Message | Andrew Chernow | 2008-01-08 22:36:51 | Re: Proposal - libpq Type System beta-0.8a (was PGparam) |