| 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: | 87y7h7kxj4.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-07-23 14:37:13 | Re: BUG #3479: contraint exclusion and locks |
| Previous Message | Andrei Badea | 2007-07-23 13:58:47 | BUG #3480: JDBC driver: getIndexInfo() returns quotes around quoted column names |