Re: archive logs recovery - Mailing list pgsql-admin

From Tom Lane
Subject Re: archive logs recovery
Date
Msg-id 23609.1157056599@sss.pgh.pa.us
Whole thread Raw
In response to Re: archive logs recovery  ("Sriram Dandapani" <sdandapani@counterpane.com>)
List pgsql-admin
"Sriram Dandapani" <sdandapani@counterpane.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

pgsql-admin by date:

Previous
From: "Sriram Dandapani"
Date:
Subject: Re: archive logs recovery
Next
From: "Sriram Dandapani"
Date:
Subject: Re: archive logs recovery