From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Rod Taylor <rbt(at)sitesell(dot)com> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Slow tab completion (7.4) |
Date: | 2004-12-24 15:44:34 |
Message-ID: | 8521.1103903074@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Rod Taylor <rbt(at)sitesell(dot)com> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-12-24 15:46:27 | Re: RC2 and open issues |
Previous Message | Alvaro Herrera | 2004-12-23 21:58:37 | Re: CreateFunctionStmt struct |