Skip site navigation (1) Skip section navigation (2)

Re: dropping a master table and all of its partitions?

From: George Nychis <gnychis(at)cmu(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Erik Jones <erik(at)myemma(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: dropping a master table and all of its partitions?
Date: 2007-02-27 13:32:47
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-general

Tom Lane wrote:
> George Nychis <gnychis(at)cmu(dot)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


In response to


pgsql-general by date

Next:From: Bill MoranDate: 2007-02-27 13:43:27
Subject: Unable to restore dump due to client encoding issues -- or, when is SQL_ASCII really UTF8
Previous:From: Rafa CominoDate: 2007-02-27 13:28:54
Subject: Bad performace of a query

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group