Re: v7.2.3 versus v7.3 -> huge performance penalty for JOIN with UNION - Mailing list pgsql-performance

From Tom Lane
Subject Re: v7.2.3 versus v7.3 -> huge performance penalty for JOIN with UNION
Date
Msg-id 20527.1038895184@sss.pgh.pa.us
Whole thread Raw
In response to Re: v7.2.3 versus v7.3 -> huge performance penalty for JOIN with UNION  ("ir. F.T.M. van Vugt bc." <ftm.van.vugt@foxi.nl>)
Responses Re: v7.2.3 versus v7.3 -> huge performance penalty for JOIN with UNION  ("Frank van Vugt" <ftm.van.vugt@foxi.nl>)
List pgsql-performance
"ir. F.T.M. van Vugt bc." <ftm.van.vugt@foxi.nl> writes:
> Any hints on this (last) one....?

>    ->  Nested Loop  (cost=0.00..643707.03 rows=3980 width=28)
>          Join Filter: (((("inner".debtor_id)::text || '-'::text) ||
> ("inner".address_seqnr)::text) = "outer".old_id)

Looks to me like debtor_id and address_seqnr are not text type, but are
being compared to things that are text.  Hard to tell exactly what's
going on though --- I suppose this query is getting rewritten by a rule?

            regards, tom lane

pgsql-performance by date:

Previous
From: li li
Date:
Subject: Is there any limitations
Next
From: "Frank van Vugt"
Date:
Subject: Re: v7.2.3 versus v7.3 -> huge performance penalty for JOIN with UNION