Re: process deadlocking on its own transactionid? - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: process deadlocking on its own transactionid?
Date
Msg-id 20130723214119.GC14652@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: process deadlocking on its own transactionid?  (Jeff Janes <jeff.janes@gmail.com>)
List 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


pgsql-general by date:

Previous
From: Jeff Janes
Date:
Subject: Re: process deadlocking on its own transactionid?
Next
From: Some Developer
Date:
Subject: Why are stored procedures looked on so negatively?