Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e71c1-0007U2-Qk for pgsql-performance@arkaria.postgresql.org; Tue, 24 Oct 2017 15:59:29 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1e71c1-0005F0-DJ for pgsql-performance@arkaria.postgresql.org; Tue, 24 Oct 2017 15:59:29 +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_2) (envelope-from ) id 1e71aH-00017C-Bk for pgsql-performance@postgresql.org; Tue, 24 Oct 2017 15:57:41 +0000 Received: from mail-1.server.selfnet.de ([141.70.126.65] helo=mail.wh-stuttgart.net) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e71a9-0005gv-MB for pgsql-performance@postgresql.org; Tue, 24 Oct 2017 15:57:40 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.wh-stuttgart.net (Postfix) with ESMTP id 361E7184D1E; Tue, 24 Oct 2017 17:57:32 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mail.selfnet.de Received: from mail.wh-stuttgart.net ([127.0.0.1]) by localhost (mail-1.server.selfnet.de [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id QxEgDgs9PHDZ; Tue, 24 Oct 2017 17:57:32 +0200 (CEST) Received: from [IPv6:2a02:200:2e00:a230:c617:5cef:bdfb:8100] (unknown [IPv6:2a02:200:2e00:a230:c617:5cef:bdfb:8100]) by mail.wh-stuttgart.net (Postfix) with ESMTPSA; Tue, 24 Oct 2017 17:57:32 +0200 (CEST) Subject: Re: performance drop after upgrade (9.6 > 10) To: Justin Pryzby Cc: Pavel Stehule , "pgsql-performance@postgresql.org" References: <20171024151803.GH21735@telsasoft.com> From: =?UTF-8?Q?Johannes_Gra=c3=abn?= Message-ID: Date: Tue, 24 Oct 2017 17:57:31 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171024151803.GH21735@telsasoft.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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 2017-10-24 17:18, Justin Pryzby wrote: > You could (re)install PG96 alongside PG10 and run a copy of the DB (even from > your homedir, or on a difference server) and pg_dump |pg_restore the relevant > tables (just be sure to specify the alternate host/port/user/etc as needed for > the restore invocation). I considered that but it is far too expensive just for getting the old query plan. The database is more than 1 TB big and replaying it from a dump to another server took us several days, primarily due to the heavy use of materialized views that are calculated over all rows of some large tables. As long as there is no safe pg_downgrade --link I'd rather keep trying to improve query performance on the current version. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance