From: Shridhar Daithankar <shridhar_daithankar@myrealbox.com>
To: Laurent Martelli <laurent@aopsys.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Join on incompatible types
Date: Wed, 19 Nov 2003 15:49:23 +0530
Message-ID: <3FBB43AB.30302@myrealbox.com> (raw)
In-Reply-To: <87u150k7mc.fsf@news.nerim.net>
References: <Pine.LNX.4.33.0310291446430.22074-100000@css120.ihs.com>
<87k75ym1v7.fsf@news.nerim.net>
<3FB9F855.7010905@myrealbox.com>
<87oev9lsgs.fsf@news.nerim.net>
<3FBB138C.4090303@myrealbox.com>
<87u150k7mc.fsf@news.nerim.net>
Laurent Martelli wrote:
>>>>>>"Shridhar" == Shridhar Daithankar <shridhar_daithankar@myrealbox.com> writes:
> Shridhar> I am stripping the analyze outputs and directly jumping to
> Shridhar> the end.
>
> Shridhar> Can you try following?
>
> Shridhar> 1. Make all fields integer in all the table.
>
> I can't do this because lists.values contains non integer data which
> do not refer to a classes.id value. It may sound weird. This is
> because it's a generic schema for a transparent persistence framework.
Fine .I understand. So instead of using a field value, can you use integer
version of that field? (Was that one of your queries used that? I deleted the OP)
> The solution for me would rather be to have varchar everywhere.
You need to cast every occurance of that varchar field appropriately, to start
with. The performance might suffer as well for numbers.
> Shridhar> 2. Try following query EXPLAIN ANALYZE SELECT * from lists
> Shridhar> join classes on classes.id=lists.value where
> Shridhar> lists.id='16'::integer;
classes.id=lists.value::integer.
Try that.
The aim is absolute type compatibility. If types aren't exactly same, the plan
is effectively dead.
<OT>
I would say postgresql enforces good habits in it's application developers, from
a cultural POV.
Had C refused to compile without such strict type compatibility, we wouldn't
have to worry about 16bit/32bit and 64 bit software. Just upgrade the compiler
and everything is damn good..:-)
I doubt if C would have so popular with such strict type checking but that is
another issue. I think pascal enforces such strict syntax.. Not sure though..
</OT>
Shridhar
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: shridhar_daithankar@myrealbox.com, laurent@aopsys.com
Subject: Re: Join on incompatible types
In-Reply-To: <3FBB43AB.30302@myrealbox.com>
* 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