Re: archive logs recovery

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Sriram Dandapani" <sdandapani(at)counterpane(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: archive logs recovery
Date: 2006-08-31 20:36:39
Message-ID: 23609.1157056599@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

"Sriram Dandapani" <sdandapani(at)counterpane(dot)com> writes:
> I have a very high traffic db with lots of table partitions. The only
> reliable way to drop the partitioned tables is to prevent any
> insert/select on the parent table , otherwise, the drop table locks out
> the inserts, and strangely enough, the drop table command goes into a
> wait state. During shutdown and restart, I switch the pg_hba.conf to
> disallow client access for a brief period when the tables are dropped.

You do know you can change pg_hba.conf without a restart?

As for the drop going into a wait state, you might want to look around
for client code that's sitting idle with an open transaction. The drop
should not block for longer than whatever is your longest transaction
touching that table.

regards, tom lane

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Sriram Dandapani 2006-08-31 20:38:48 Re: archive logs recovery
Previous Message Sriram Dandapani 2006-08-31 20:27:02 Re: archive logs recovery