Re: dropping a master table and all of its partitions? - Mailing list pgsql-general

From George Nychis
Subject Re: dropping a master table and all of its partitions?
Date
Msg-id 45E432FF.3040201@cmu.edu
Whole thread Raw
In response to Re: dropping a master table and all of its partitions?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: dropping a master table and all of its partitions?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general

Tom Lane wrote:
> George Nychis <gnychis@cmu.edu> writes:
>> Here is an exact script which generates this every single time...
>> After you're done running the ruby script:
>> DROP TABLE testflows CASCADE;
>
> I tweaked the ruby script to emit the SQL commands into a script file,
> which proved to issue 1765 CREATE TABLE commands (one parent and 1764
> children) and 1764 CREATE RULE commands (one per child table).  On my
> test installation the creation script runs about 6m15s, while
> "DROP TABLE testflows CASCADE" runs about 3m4s.  While neither number
> is exactly awe-inspiring, I'm not seeing why you think the DROP is
> particularly broken?
>
>             regards, tom lane
Then maybe it's a bug in my version of postgresql, what version are you using?
Because that DROP TABLE testflows CASCADE; runs for ~5 minutes and then dies on
my side.  It never finishes.

- George


>

pgsql-general by date:

Previous
From: "Rafa Comino"
Date:
Subject: Bad performace of a query
Next
From: Bill Moran
Date:
Subject: Unable to restore dump due to client encoding issues -- or, when is SQL_ASCII really UTF8