On Tue, Mar 18, 2014 at 3:42 AM, Amit Kapila <amit.kapil...@gmail.com> wrote:
> The message for exclusive lock on tuple print the database information.

It is true that it is possible to have a deadlock or lock chains that
involves locks on other databases.
In this example the table "test" is not in the database that just
logged the deadlock.

STATEMENT:  create role test;
ERROR:  deadlock detected
DETAIL:  Process 8968 waits for ShareLock on transaction 1067; blocked
by process 8973.
        Process 8973 waits for ShareLock on transaction 1064; blocked
by process 8971.
        Process 8971 waits for ShareLock on transaction 1062; blocked
by process 8968.
        Process 8968: create role test;
        Process 8973: insert into test values (2);
        Process 8971: create role test2;


Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to