Rod Taylor <[EMAIL PROTECTED]> writes:
> It seems that with more than a few thousand structures in pg_class, tab
> completion seems to take quite a long time in the en_US locale.
> Simply switching the where clauses around gets a substantial performance
> increase.
Hm. There's no guarantee that the planner will evaluate the WHERE
clauses in the same order you write them, but it does seem to work that
way for these particular queries at the moment, so we may as well write
the clauses in the best order. You're right that the foo_is_visible()
family of functions are pretty slow...
regards, tom lane
---------------------------(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
