Re: [PERFORM] Hash Anti Join performance degradation

From: Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: 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 01:11:16
Message-ID: BANLkTikDKUF53_MhP-T9y9NM7a8z40djXA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

2011/6/1 Robert Haas <robertmhaas(at)gmail(dot)com>:
> On Tue, May 31, 2011 at 8:43 PM, Cédric Villemain
> <cedric(dot)villemain(dot)debian(at)gmail(dot)com> wrote:
>> Yes, while here I noticed that the query was long to be killed.
>> I added a CHECK_FOR_INTERRUPT() in the for(;;) loop in nodeHashjoin.c.
>> It fixes the delay when trying to kill but I don't know about
>> performance impact this can have in this place of the code.
>
> Well, seems easy enough to find out: just test the query with and
> without your patch (and without casserts).  If there's no measurable
> difference on this query, there probably won't be one anywhere

Oh damned, I am currently with an eeepc, I'll need 2 days to bench that :-D
I'll see tomorow.
.
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>

--
Cédric Villemain               2ndQuadrant
http://2ndQuadrant.fr/     PostgreSQL : Expertise, Formation et Support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2011-06-01 01:13:25 Re: [BUGS] BUG #6046: select current_date crashes postgres
Previous Message Brendan Jurd 2011-06-01 01:05:39 Re: [HACKERS] DOCS: SGML identifier may not exceed 44 characters

Browse pgsql-performance by date

  From Date Subject
Next Message Craig Ringer 2011-06-01 01:40:52 Re: Delete performance
Previous Message Robert Haas 2011-06-01 00:55:38 Re: [PERFORM] Hash Anti Join performance degradation