"Wayne Conrad" <wcon...@yagni.com> writes:
> "VACUUM FULL ANALYZE VERBOSE" on a "deadlocks" with other SQL statements.
What this looks like to me is an application problem. In each case
you show, the only backends that actually *have* the lock are
"<IDLE> in transaction", ie they are waiting for their clients to
issue another command or close the transaction. The other queries
won't be able to make any forward progress until those transactions
complete and release their locks.
> To summarize the above output: there are three statements, each waiting on
> the other two:
No, you're reading it wrong. The sessions with granted=false are waiting
on the ones with granted=true.
It's conceivable that this actually is a deadlock situation, if the
connected clients are interrelated and are coded so that those other
queries must finish before they will do anything more. But you'll have
to break such a deadlock on the application side; Postgres has no way to
know what's happening.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
