From: Bruno Wolff III <bruno@wolff.to>
To: pgsql-performance@postgresql.org
Subject: Re: Using bigint needs explicit cast to use the index
Date: Mon, 8 Mar 2004 10:33:20 -0600
Message-ID: <20040308163320.GA32497@wolff.to> (raw)
In-Reply-To: <20040308160525.GA25077@phlogiston.dyndns.org>
References: <001101c404a3$fb34d320$fd08a8c0@steve>
<20040308160525.GA25077@phlogiston.dyndns.org>
On Mon, Mar 08, 2004 at 11:05:25 -0500,
Andrew Sullivan <ajs@crankycanuck.ca> wrote:
>
> "Intended", no. "Expected", yes. This topic has had the best
> Postgres minds work on it, and so far nobody's come up with a
> solution. There was a proposal to put in a special-case automatic
> fix for int4/int8 in 7.4, but I don't know whether it made it in.
This is handled better in 7.5. Instead of doing things deciding what
types of type conversion to do, a check is make for cross type conversion
functions that could be used for an index scan. This is a general solution
that doesn't result in unexpected type conversions.
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: bruno@wolff.to
Subject: Re: Using bigint needs explicit cast to use the index
In-Reply-To: <20040308163320.GA32497@wolff.to>
* 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