Re: BUG #3479: contraint exclusion and locks - Mailing list pgsql-bugs

From Gregory Stark
Subject Re: BUG #3479: contraint exclusion and locks
Date
Msg-id 87y7h7kxj4.fsf@oxford.xeocode.com
Whole thread Raw
In response to BUG #3479: contraint exclusion and locks  ("Tiago Jacobs" <tiago@mdtestudio.com.br>)
Responses Re: BUG #3479: contraint exclusion and locks
List pgsql-bugs
"Tiago Jacobs" <tiago@mdtestudio.com.br> writes:

> oh-ow... It waits while the table (That is not used) is locked.
>
> Even that the final plan dont use tab_2007_07, it wait for unlock of table
> for make the plan.

Well one of the reasons exclusive locks are taken are to make changes to
constraints.

> So, if I`m running a VACUUM on specific table, all the querys on the
> "master" table don't work.

VACUUM doesn't take an exclusive lock. VACUUM is designed to be run regularly
without interfering with full use of the table.

You're not running VACUUM FULL are you? That's much more intrusive and
shouldn't be needed in regular operation.

--
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com

pgsql-bugs by date:

Previous
From: "Andrei Badea"
Date:
Subject: BUG #3480: JDBC driver: getIndexInfo() returns quotes around quoted column names
Next
From: Tom Lane
Date:
Subject: Re: BUG #3479: contraint exclusion and locks