Could you roll in a temporary pg_hba.conf, issue the pg_ctl reload command to reread that and then identify those ips using ps, and kill -TERM them? After your maintenance, rotate back in your full pg_hba.conf and reload it.
From: pgsql-admin-ow...@postgresql.org [mailto:pgsql-admin-ow...@postgresql.org] On Behalf Of Little, Douglas Sent: Thursday, October 28, 2010 7:39 AM To: pgsql-admin@postgresql.org Subject: [ADMIN] Forced quiesce Hi, We're having to vacuum full the system tables everyday due to the number of temp table drop/creates. We're finding that if anyone tries to execute a job during the maintenance period, it often hangs the db. Is there a way that we can force the db to quiesce? Or lock out users. Luckly, most users are coming in thru a network VIP, so all client IP's are the same. Thanks in advance. Doug Little Sr. Data Warehouse Architect | Enterprise Data Management | Orbitz Worldwide 500 W. Madison, Suite 1000 Chicago IL 60661| Office 312.260.2588 | Fax 312.894.5164 | Cell 847-997-5741 douglas.lit...@orbitz.com<mailto:douglas.lit...@orbitz.com> [cid:image001.jpg@01CB7674.0890EAB0] orbitz.com<http://www.orbitz.com/> | ebookers.com<http://www.ebookers.com/> | hotelclub.com<http://www.hotelclub.com/> | cheaptickets.com<http://www.cheaptickets.com/> | ratestogo.com<http://www.ratestogo.com/> | asiahotels.com<http://www.asiahotels.com/>
<<inline: image001.jpg>>
