Re: [PERFORM] Hash Anti Join performance degradation

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com>, panam <panam(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PERFORM] Hash Anti Join performance degradation
Date: 2011-06-01 20:58:36
Message-ID: BANLkTimXuMGGv_vPQrQjR17K3QomP8NnQw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

On Wed, Jun 1, 2011 at 4:47 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> I guess the real issue here is that m1.id < m2.id has to be evaluated
>> as a filter condition rather than a join qual.
>
> Well, if you can invent an optimized join technique that works for
> inequalities, go for it ... but I think you should get at least a
> PhD thesis out of that.

Sounds good, except that so far NOT getting a PhD seems like a much
better financial prospect. :-)

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-06-01 21:02:51 Re: [PERFORM] Hash Anti Join performance degradation
Previous Message Andrew Chernow 2011-06-01 20:48:55 Re: PQdeleteTuple function in libpq

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2011-06-01 21:02:51 Re: [PERFORM] Hash Anti Join performance degradation
Previous Message Tom Lane 2011-06-01 20:47:36 Re: [PERFORM] Hash Anti Join performance degradation