Re: Query planner isn't using my indices

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Shaun Thomas <sthomas(at)townnews(dot)com>
Cc: PostgreSQL general list <pgsql-general(at)postgresql(dot)org>
Subject: Re: Query planner isn't using my indices
Date: 2002-01-09 20:50:04
Message-ID: 14952.1010609404@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Shaun Thomas <sthomas(at)townnews(dot)com> writes:
> Can anyone explain this to me? Anyone at all? I mean, what logical
> reason is there to leave the database so crippled?

Feel free to step right up and fix it. This is an open-source project.

Whining aside, the reason why these restrictions still exist is that
we have an extensible type system and so we don't really want to put
hard-wired knowledge about different types into the parser or optimizer.
The difficult part is to design a general-purpose, extensible framework
in which these desired conversions can be specified.

There have been prior discussions of how to do this (see the pghackers
archives); but no one's put forward a really satisfactory proposal yet.
If anyone had, it'd probably have been implemented by now --- there
isn't anyone here who likes the current behavior any more than you do.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2002-01-09 21:03:29 Re: Question regarding VACUUM ANALYZE ERROR . . .
Previous Message Tom Lane 2002-01-09 20:22:55 Re: pg_xsetlog