From: | Shridhar Daithankar <shridhar_daithankar(at)myrealbox(dot)com> |
---|---|
To: | Laurent Martelli <laurent(at)bearteam(dot)org> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Join on incompatible types |
Date: | 2003-11-18 10:45:41 |
Message-ID: | 3FB9F855.7010905@myrealbox.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Laurent Martelli wrote:
>>>>>>"scott" == scott marlowe <scott(dot)marlowe(at)ihs(dot)com> writes:
>
>
> [...]
>
> scott> Note here:
>
> scott> Merge Join (cost=1788.68..4735.71 rows=1 width=85) (actual
> scott> time=597.540..1340.526 rows=20153 loops=1) Merge Cond:
> scott> ("outer".id = "inner".id)
>
> scott> This estimate is WAY off. Are both of those fields indexed
> scott> and analyzed? Have you tried upping the statistics target on
> scott> those two fields? I assume they are compatible types.
>
> Should I understand that a join on incompatible types (such as integer
> and varchar) may lead to bad performances ?
Conversely, you should enforce strict type compatibility in comparisons for
getting any good plans..:-)
Shridhar
From | Date | Subject | |
---|---|---|---|
Next Message | Laurent Martelli | 2003-11-18 13:24:51 | Re: Join on incompatible types |
Previous Message | Laurent Martelli | 2003-11-18 10:01:48 | Join on incompatible types |