Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UXdJT-0004gr-PL for pgsql-performance@arkaria.postgresql.org; Wed, 01 May 2013 20:07:39 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1UXdJT-0000qk-7c for pgsql-performance@arkaria.postgresql.org; Wed, 01 May 2013 20:07:39 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UXdJR-0000pf-PS for pgsql-performance@postgresql.org; Wed, 01 May 2013 20:07:37 +0000 Received: from mail-da0-x235.google.com ([2607:f8b0:400e:c00::235]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UXdJO-000537-Vk for pgsql-performance@postgresql.org; Wed, 01 May 2013 20:07:37 +0000 Received: by mail-da0-f53.google.com with SMTP id n34so790089dal.12 for ; Wed, 01 May 2013 13:07:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:subject:from:to:cc:date:in-reply-to :references:content-type:x-mailer:mime-version :content-transfer-encoding:x-gm-message-state; bh=TApLpaXSQm6NIRamrf9WTjJff1eecluhjwS4h41eQo8=; b=dNSHIhgB2MrFoTFSZf2+JliJn4ha8SSfuF3wwqSSi7sGf8GSXSHNROlQtSRxfE51+U W0c8RVHsjkprSdzajLUQJGTBCXKKkkosSWA7nBCUd+GeWG17tQpxRJUsT9aaRgCflJNe zYScBQYyZvPOKfIi55a8Rq34kyMM/Wk3YDzp49rdl2+i3EmUcsjFb5lnCS0YBFv9+HcF xiDd+1SWtcBN/j3QzETimKx3SkKEyi5Vv17xsYAWnNhoIIwcJXRzOxMQwHmELQnohQ7M 5wzn5B5eKBrEdU1q6VUmbWvWtcLwongYpxWCPLqLfTYnHio2isabTxKlgv9f8i4wDL7h TNLA== X-Received: by 10.66.197.136 with SMTP id iu8mr6774538pac.0.1367438853588; Wed, 01 May 2013 13:07:33 -0700 (PDT) Received: from [192.168.0.101] (c-69-181-249-16.hsd1.ca.comcast.net. [69.181.249.16]) by mx.google.com with ESMTPSA id dg5sm4138932pbc.29.2013.05.01.13.07.32 for (version=SSLv3 cipher=RC4-SHA bits=128/128); Wed, 01 May 2013 13:07:32 -0700 (PDT) Message-ID: <1367438854.2188.60.camel@jdavis> Subject: Re: [BUGS] BUG #8130: Hashjoin still gives issues From: Jeff Davis To: Stefan de Konink Cc: Tom Lane , pgsql-performance@postgresql.org Date: Wed, 01 May 2013 13:07:34 -0700 In-Reply-To: References: <3469.1367421052@sss.pgh.pa.us> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.6.2-0ubuntu0.1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQlV0cuZi0W3kgbI0+AMsw/JRAZm3JV0+WyRVYH+nw3z0q/LqXE+pLWZ1TtiXZUvRwOQqaQe X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On Wed, 2013-05-01 at 17:44 +0200, Stefan de Konink wrote: > Combined with the recent bugfix regarding hash > estimation, it gives me a good indication that there might be a bug. To which recent bugfix are you referring? The best venue for fixing an issue like this is pgsql-performance -- it doesn't make too much difference whether it's a "bug" or not. Performance problems sometimes end up as bugs and sometimes end up being treated more like an enhancement; but most of the progress is made on pgsql-performance regardless. Regards, Jeff Davis -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance