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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "ir(dot) F(dot)T(dot)M(dot) van Vugt bc(dot)" <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
Cc: Postgresql performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: v7.2.3 versus v7.3 -> huge performance penalty for JOIN with UNION
Date: 2002-12-03 05:59:44
Message-ID: 20527.1038895184@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

"ir. F.T.M. van Vugt bc." <ftm(dot)van(dot)vugt(at)foxi(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Frank van Vugt 2002-12-03 09:38:10 Re: v7.2.3 versus v7.3 -> huge performance penalty for JOIN with UNION
Previous Message li li 2002-12-03 05:46:43 Is there any limitations