Re: locked backend

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Csaba Nagy <nagy(at)ecircle-ag(dot)com>
Cc: Postgres general mailing list <pgsql-general(at)postgresql(dot)org>
Subject: Re: locked backend
Date: 2005-11-16 18:41:31
Message-ID: 9599.1132166491@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Csaba Nagy <nagy(at)ecircle-ag(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Greg Stark 2005-11-16 18:57:56 Re: locked backend
Previous Message Ben 2005-11-16 18:28:40 Re: Rebranding PostgreSQL