From: Neil Conway <neilc@samurai.com>
To: Reece Hart <reece@in-machina.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: explicit casting required for index use
Date: Mon, 27 Oct 2003 04:18:53 -0500
Message-ID: <1067246333.457.12.camel@tokyo> (raw)
In-Reply-To: <1067104140.16297.125.camel@tallac>
References: <1067104140.16297.125.camel@tallac>
On Sat, 2003-10-25 at 13:49, Reece Hart wrote:
> Having to explicitly cast criterion is very non-intuitive. Moreover,
> it seems quite straightforward that PostgreSQL might incorporate casts
This is a well-known issue with the query optimizer -- search the
mailing list archives for lots more information. The executive summary
is that this is NOT a trivial issue to fix, and it hasn't been fixed in
7.4, but there is some speculation on how to fix it at some point in the
future.
-Neil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: neilc@samurai.com, reece@in-machina.com
Subject: Re: explicit casting required for index use
In-Reply-To: <1067246333.457.12.camel@tokyo>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox