| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Kevin Goess <kgoess(at)bepress(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: process deadlocking on its own transactionid? |
| Date: | 2013-07-23 21:41:20 |
| Message-ID: | 20130723214119.GC14652@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Jeff Janes escribió:
> The transaction it is waiting for is in the transactionid column,
> which is not in your select list. The virtualxid column seems pretty
> useless to me, I don't really know why it is there.
If you do CREATE INDEX CONCURRENTLY and it has to wait for other
processes to finish their current transactions (in order for them to
release their snapshots, which is what it needs to ensure the index can
be enabled), it will use the virtualxid.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Some Developer | 2013-07-24 00:29:14 | Why are stored procedures looked on so negatively? |
| Previous Message | Jeff Janes | 2013-07-23 21:36:51 | Re: process deadlocking on its own transactionid? |