Tom Lane wrote:
George Nychis <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
