Skip site navigation (1) Skip section navigation (2)

Re: BUG #3479: contraint exclusion and locks

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Tiago Jacobs" <tiago(at)mdtestudio(dot)com(dot)br>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #3479: contraint exclusion and locks
Date: 2007-07-23 14:25:03
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
"Tiago Jacobs" <tiago(at)mdtestudio(dot)com(dot)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

> 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

In response to


pgsql-bugs by date

Next:From: Tom LaneDate: 2007-07-23 14:37:13
Subject: Re: BUG #3479: contraint exclusion and locks
Previous:From: Andrei BadeaDate: 2007-07-23 13:58:47
Subject: BUG #3480: JDBC driver: getIndexInfo() returns quotes around quoted column names

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group