Re: locked backend

Csaba Nagy <nagy@ecircle-ag.com> writes:
> The situation (diagnosed via pg_stat_activity): one table was locked by
> an update, a VACUUM ANALYZE was running for the same table (triggered by
> autovacuum), and a handful of inserts were waiting on the same table.

Updates do not block inserts, and neither does vacuum, so there's
something you're not telling us.  In particular an UPDATE wouldn't
take an ExclusiveLock on the table, so that lock must have come from
some other operation in the same transaction.

            regards, tom lane