Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZBkzf-0004Tg-Od for pgsql-performance@arkaria.postgresql.org; Sun, 05 Jul 2015 14:34:07 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZBkze-0001IA-QX for pgsql-performance@arkaria.postgresql.org; Sun, 05 Jul 2015 14:34:06 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZBkzc-0001Hx-KF for pgsql-performance@postgresql.org; Sun, 05 Jul 2015 14:34:04 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZBkzU-0007DI-JU for pgsql-performance@postgresql.org; Sun, 05 Jul 2015 14:34:03 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id t65EXPnv010846; Sun, 5 Jul 2015 10:33:25 -0400 From: Tom Lane To: Andres Freund cc: "Mkrtchyan, Tigran" , pgsql-performance Subject: Re: 9.5alpha1 vs 9.4 In-reply-to: <20150705125403.GD24494@alap3.anarazel.de> References: <1897514812.2949286.1436094651680.JavaMail.zimbra@desy.de> <20150705125403.GD24494@alap3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Sun, 05 Jul 2015 14:54:03 +0200" Date: Sun, 05 Jul 2015 10:33:25 -0400 Message-ID: <10845.1436106805@sss.pgh.pa.us> X-Pg-Spam-Score: -2.5 (--) 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 Andres Freund writes: > On 2015-07-05 13:10:51 +0200, Mkrtchyan, Tigran wrote: >> today I have update my test system to 9.5alpha1. >> Most of the operations are ok, except delete. >> I get ~1000 times slower! >> 255.88 | 566.11 | 452 | DELETE FROM t_inodes WHERE ipnfsid=$1 AND inlink = ? > That certainly should not be the case. Could you show the query plan for > this statement in both versions? EXPLAIN ANALYZE, please. I'm wondering about a missing index on some foreign-key-involved column. That would show up as excessive time in the relevant trigger ... regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance