When I modify the trigger, I noticed that postgres restarted. Not sure why, but it happens when it is being executed. This behaviour is consistent. Dropping the trigger is not viable as inserts happen 24x7 at a high rate. -----Original Message----- From: Jim C. Nasby [mailto:jnasby@xxxxxxxxxxxxx] Sent: Tuesday, August 15, 2006 2:32 PM To: Sriram Dandapani Cc: pgsql-admin@xxxxxxxxxxxxxx Subject: Re: [ADMIN] dropping partitioned table waits forever On Mon, Aug 14, 2006 at 03:32:10PM -0700, Sriram Dandapani wrote: > Hi > > > > I have a table partitioned on a daily basis. Data is constantly inserted > in this table. When I attempt to drop a partition that is not used(i.e > previous day's), the drop table waits for a loooong time.This is > probably due to the fact that the old partitioned table is being > referenced in a query plan(the insert into the parent table uses > triggers). > > How can I prevent the locking out of the drop table? I tried truncate > table but it is worse. It locks out the inserts in the parent table and > then it waits.(hence causing a deadlock) What about dropping/changing the trigger? -- Jim C. Nasby, Sr. Engineering Consultant jnasby@xxxxxxxxxxxxx Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
