| From: | "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl> |
|---|---|
| To: | "Keary Suska" <hierophant(at)pcisys(dot)net> |
| Cc: | "Postgres-Interfaces" <pgsql-interfaces(at)postgresql(dot)org> |
| Subject: | Re: query optimization on prepared statement through |
| Date: | 2006-12-05 04:05:55 |
| Message-ID: | 11196.125.24.218.106.1165291555.squirrel@webmail.xs4all.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
On Tue, December 5, 2006 00:25, Keary Suska wrote:
> Note that even if queries use an updated query plan, the planner may not
> choose the best plan anyway. There are various parameters that may effect
> the planner, such as inferred types and joins across different (although
> compatible) column types. This last bit may have been solved recently,
> however.
Also, IIRC it's possible to create indexes on function results. So if you
have, say, an integer column X then you could possibly index that table on
"X converted to text."
Jeroen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fayza Sultan | 2006-12-07 19:54:51 | Unable to Install on Windows (using MINGW) with PL/TCL and PL/Perl libraries support |
| Previous Message | Keary Suska | 2006-12-04 17:25:12 | Re: query optimization on prepared statement through |