Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e2FzR-0002ER-5S for pgsql-performance@arkaria.postgresql.org; Wed, 11 Oct 2017 12:19:57 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1e2FzQ-0003SW-4Z for pgsql-performance@arkaria.postgresql.org; Wed, 11 Oct 2017 12:19:56 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e2FzO-0003RU-GE for pgsql-performance@postgresql.org; Wed, 11 Oct 2017 12:19:54 +0000 Received: from mail-1.server.selfnet.de ([141.70.126.65] helo=mail.wh-stuttgart.net) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e2FzF-0005Bp-Uj for pgsql-performance@postgresql.org; Wed, 11 Oct 2017 12:19:52 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.wh-stuttgart.net (Postfix) with ESMTP id C9EB518336D for ; Wed, 11 Oct 2017 14:19:40 +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 fNNRODXue5ax for ; Wed, 11 Oct 2017 14:19:40 +0200 (CEST) Received: from mail-oi0-f41.google.com (mail-oi0-f41.google.com [209.85.218.41]) by mail.wh-stuttgart.net (Postfix) with ESMTPSA for ; Wed, 11 Oct 2017 14:19:40 +0200 (CEST) Received: by mail-oi0-f41.google.com with SMTP id g125so2558774oib.12 for ; Wed, 11 Oct 2017 05:19:40 -0700 (PDT) X-Gm-Message-State: AMCzsaWWPJ97qzE0+0G+MrOkbTVp2/3g4UfHX6uhOhO1ghG+UNHIr3gO EA031RHEvEpdEwfrJ408CohiVPIzbnpHLJMPZ98= X-Google-Smtp-Source: AOwi7QAiEZGp/65Rq4gQn/4N6LuP9SCBZaZSkoVWVZ/+Zg92kzoSDjs1ZwrrTDlRR1b5c971WIFft3ijuULM7yXjSDY= X-Received: by 10.157.17.175 with SMTP id v44mr3540737otf.450.1507724379249; Wed, 11 Oct 2017 05:19:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.67.138 with HTTP; Wed, 11 Oct 2017 05:19:08 -0700 (PDT) In-Reply-To: References: From: =?UTF-8?Q?johannes_gra=C3=ABn?= Date: Wed, 11 Oct 2017 14:19:08 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: performance drop after upgrade (9.6 > 10) To: Pavel Stehule Cc: "pgsql-performance@postgresql.org" Content-Type: text/plain; charset="UTF-8" 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, Oct 11, 2017 at 1:11 PM, Pavel Stehule wrote: > have you fresh statistics? After upgrade is necessary to run ANALYZE command Yes, that was missing indeed. I did ANALYZE but apparently on all databases but this one. I could have guessed that 1,098,956,679,131,935,754,413,282,631,696,252,928 is not a reasonable cost value. Thanks, Pavel. Best Johannes -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance