| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
| Cc: | pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: Improve warnings around CREATE INDEX CONCURRENTLY |
| Date: | 2011-05-24 20:48:07 |
| Message-ID: | 1306269968-sup-2890@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Excerpts from Greg Smith's message of mar may 24 03:56:59 -0400 2011:
> What makes it worse is that the wait shows up as a virtualxid one, which
> doesn't pop up on many common samples of things to look for in
> pg_locks. It would be reasonable but also incorrect for admins to
> assume a table one would be visible if running into the case alluded to
> in the docs. The serial way locks are obtained is unexpected too.
Incidentally, this is one of the things that Jim Nasby wanted exposed
somehow so that these problems are more easily diagnosed. I dropped the
ball on that one, but I'll be picking it up again at some point.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2011-05-24 21:06:07 | Re: Improve warnings around CREATE INDEX CONCURRENTLY |
| Previous Message | Greg Smith | 2011-05-24 07:56:59 | Improve warnings around CREATE INDEX CONCURRENTLY |