It seemed a tad excessive to me, at least for routine regression testing. What do you think of making it a separate test script and adding it to "make bigcheck", as we did once with the numeric_big tests?
I'm not sure I see the point: I would guess that the rate at which we're expanding the regression tests is slower than the rate of performance increase of the average machine someone is running Postgres on (so in a sense the regression tests are speeding up over time). If at some point we add some regression tests that take a considerably longer amount of time to run, this sounds good -- I just don't think we've reached that point yet.
-Neil
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
