The jdbc inserts go into the main parent table and check constraints redirect them to child tables. If I were to drop the rule, that would immediately affect the inserts and they would go the the parent table. And I cannot lock the parent due to the problem I mentioned earlier. -----Original Message----- From: Tom Lane [mailto:tgl@xxxxxxxxxxxxx] Sent: Friday, September 29, 2006 2:38 PM To: Sriram Dandapani Cc: Matthew T. O'Connor; pgsql-admin@xxxxxxxxxxxxxx Subject: Re: [ADMIN] autovacuum ignore tables "Sriram Dandapani" <sdandapani@xxxxxxxxxxxxxxx> writes: > Real question is: Why do the INSERTS go into wait state as soon as the > lock table statement is issued on the parent? If you were just inserting directly into other child tables, a lock on either the parent or the target child table shouldn't affect them. I wonder if you are using conditional rules to redirect the inserts, and the rules include a reference to the target table? If that's the case, you really need to drop the relevant rule before you remove the child table, anyway. regards, tom lane
