Re: Higher chance of deadlock due to ANALYZE VERBOSE / SHARE UPDATE EXCLUSIVE?

Dean Toader <deant@mirthcorp.com> writes:
> Can anyone see an increased possibility of deadlock occurring with
> ANALYZE VERBOSE (initiated by �vacuumdb -a --analyze-only --verbose -U postgres�
> command run once every 24 hrs on a cronjob schedule), VACUUM (initiated by autovacuum)
> and say ... a long running UPDATE (initiated by a JEE application)
> all happening concurrently on the same table?

If an autovacuum is part of a deadlock, the deadlock detector should
preferentially kill the autovacuum transaction.  Is that not happening
for you?  But in any case, whether that happens or not, SHARE UPDATE
EXCLUSIVE doesn't block UPDATE commands, so that the case you describe
above is not a deadlock.  You would have to be doing some kind of DDL
on the table in question to have any risk.

            regards, tom lane