I have a high traffic table which is populated by a trigger on another table. This high traffic table is partitioned by day. When I issue a drop table on a child table..it goes into a wait state AND puts all jdbc inserts in a wait state.(in short..a deadlock). I can repeat this use case any time. The only way to guarantee all drops to work is to briefly shutdown , modify pg_hba.conf to disallow client access, restart and issue the drop commands (followed by restoration of original pg_hba.conf) -----Original Message----- From: Tom Lane [mailto:tgl@xxxxxxxxxxxxx] Sent: Monday, September 18, 2006 1:32 PM To: Sriram Dandapani Cc: pgsql-admin@xxxxxxxxxxxxxx Subject: Re: [ADMIN] autovacuum ignore tables "Sriram Dandapani" <sdandapani@xxxxxxxxxxxxxxx> writes: > I am trying to get autovacuum to complete quicker and prevent Xactn > wraparound (currently, it takes very long and due to the fact that I > have to restart the database for maintenance purposes), autovacuum never > finishes.) Why are you restarting the database? There is no "maintenance purpose" I'm aware of that requires routine postmaster restarts. As for suppressing autovac on specific tables, see the pg_autovacuum system catalog. regards, tom lane
