From: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
To: pgsql-performance@postgresql.org
Subject: Re: Attempt at work around of int4 query won't touch int8 index ...
Date: Mon, 15 Sep 2003 13:12:28 +0530
Message-ID: <3F65BABC.32672.38837688@localhost> (raw)
In-Reply-To: <20901.1063248257@sss.pgh.pa.us>
References: <2756862E-E3F5-11D7-8513-000A9566A412@socialserve.com>
On 10 Sep 2003 at 22:44, Tom Lane wrote:
> James Robinson <jlrobins@socialserve.com> writes:
> > Is this just a dead end, or is there some variation of this that might
> > possibly work, so that ultimately an undoctored literal number, when
> > applied to an int8 column, could find an index?
>
> I think it's a dead end. What I was playing with this afternoon was
> removing the int8-and-int4 comparison operators from pg_operator.
> It works as far as making "int8col = 42" do the right thing, but I'm
> not sure yet about side-effects.
Is it possible to follow data type upgrade model in planner? Something like in
C/C++ where data types are promoted upwards to find out better plan?
int2->int4->int8->float4->float8 types.
That could be a clean solution..
just a thought..
Bye
Shridhar
--
Hlade's Law: If you have a difficult task, give it to a lazy person -- they
will find an easier way to do it.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: shridhar_daithankar@persistent.co.in
Subject: Re: Attempt at work around of int4 query won't touch int8 index ...
In-Reply-To: <3F65BABC.32672.38837688@localhost>
References: <2756862E-E3F5-11D7-8513-000A9566A412@socialserve.com> <3F65BABC.32672.38837688@localhost>
* 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