Search Postgresql Archives

Re: process deadlocking on its own transactionid?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux