Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XyWMV-0002qK-Vc for pgsql-performance@arkaria.postgresql.org; Wed, 10 Dec 2014 01:46:44 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XyWMV-0004Nt-EL for pgsql-performance@arkaria.postgresql.org; Wed, 10 Dec 2014 01:46:43 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XyWMU-0004Lh-3y for pgsql-performance@postgresql.org; Wed, 10 Dec 2014 01:46:42 +0000 Received: from 01.zmailcloud.com ([192.198.85.104] helo=mx-out-1.zmailcloud.com) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XyWMP-00062v-SI for pgsql-performance@postgresql.org; Wed, 10 Dec 2014 01:46:40 +0000 Received: from smtp.01.com (smtp.01.com [10.10.0.43]) by mx-out-1.zmailcloud.com (Postfix) with ESMTP id 20244566481; Tue, 9 Dec 2014 19:46:37 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 107C0A06E1; Tue, 9 Dec 2014 19:46:37 -0600 (CST) X-Virus-Scanned: amavisd-new at smtp-out-1.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g8kV_pisWekW; Tue, 9 Dec 2014 19:46:36 -0600 (CST) Received: from smtp.01.com (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id D9796A0781; Tue, 9 Dec 2014 19:46:36 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id B04CEA0777; Tue, 9 Dec 2014 19:46:36 -0600 (CST) X-Virus-Scanned: amavisd-new at smtp-out-1.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ha4ENsHEkn2Q; Tue, 9 Dec 2014 19:46:36 -0600 (CST) Received: from [172.47.23.103] (50-0-89-106.dsl.dynamic.fusionbroadband.com [50.0.89.106]) by smtp-out-1.01.com (Postfix) with ESMTPSA id 177ADA06E1; Tue, 9 Dec 2014 19:46:35 -0600 (CST) Message-ID: <5487A5FA.8080603@agliodbs.com> Date: Tue, 09 Dec 2014 17:46:34 -0800 From: Josh Berkus Organization: PostgreSQL Experts Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Simon Riggs , Merlin Moncure CC: postgres performance list Subject: Re: Yet another abort-early plan disaster on 9.3 References: <541A2335.3060100@agliodbs.com> <541DC87F.3030800@agliodbs.com> <5420B71C.6010208@agliodbs.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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 12/05/2014 08:04 AM, Simon Riggs wrote: > On 6 December 2014 at 00:45, Merlin Moncure wrote: > >> Neat -- got any test cases (would this have prevented OP's problem)? > > No test case was posted, so I am unable to confirm. > > A test case I produced that appears to be the same issue is fixed. > > I await confirmation from the OP. > So that's proprietary/confidential data. However, the company involved has a large testbed and I could test their data using a patched version of Postgres. In 3 months their data distribution has drifted, so I'll need to do some work to recreate the original bad plan circumstances. I'll keep you posted on how the patch works for that setup. It would be great to come up with a generic/public test for a bad abort-early situation. Ideas? -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance