Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rx99c-006dkI-BC for pgsql-general@arkaria.postgresql.org; Wed, 17 Apr 2024 17:33:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rx99a-00DQ3d-0H for pgsql-general@arkaria.postgresql.org; Wed, 17 Apr 2024 17:33:02 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rx99Z-00DQ3V-It for pgsql-general@lists.postgresql.org; Wed, 17 Apr 2024 17:33:01 +0000 Received: from mail-lj1-x22f.google.com ([2a00:1450:4864:20::22f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rx99X-003KKL-2F for pgsql-general@lists.postgresql.org; Wed, 17 Apr 2024 17:33:00 +0000 Received: by mail-lj1-x22f.google.com with SMTP id 38308e7fff4ca-2d094bc2244so66274041fa.1 for ; Wed, 17 Apr 2024 10:32:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713375177; x=1713979977; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=dIcJ2Ac+F25HFHKOTb+swknlevshUUfQdmdtko1yicw=; b=N69jZiV+nh5K3EHUumBMyFZOvThTGilyf2H6n8PHMYQ+yrQNYJpvaIuxy1s7ioCMLz SeNoLSHzHPwvugh4U0R2DTNH2eXG5rkZlxoxhIt7i9V6KwLO23vK89lAwIwmnaenaRCY PT95DHC//3kwQRinDNO2Rp4zLCG+/CnjglNzTvYyIRHJkRC2xddieWw7G6xuS2+tmJ01 yDMhF+PzXg7MtYqN+sftnAWJkCoSH7PDY7IPQbJultzJk5Yzfbv0iqAGE9Ivu72xgY4C L+RXeI6ceOGh5YlQorg/PcAt5Q9EZKp8PWR1aRhM5L9IF85le0NfecS5L7fzQywPyVbY sDSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713375177; x=1713979977; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=dIcJ2Ac+F25HFHKOTb+swknlevshUUfQdmdtko1yicw=; b=JKXfDv8kxkiJpl3BzQyAou3Q0nhtsEIehKVKoxaMraILLrTf1UOA/eGe/sLRrBDrdT +gPyjq255OFa9wPhGxEJD/AGPztownhR9EntayNSwSzinbRGh356tiU1OnNFJ8Z6slPW 1q9kHortAfq/ZoG3gfXFhG6FQMkVrupXHYv90Au9j5YsjlWI7JRMLA1ZsfIBuQ8zWwkf n7jRAPNggJktZO2VBLJZozIJxc6/5BGkMGTFEvTRoMEMFXiABpU9omCBD4rJDdsQ1u16 030LHNw2td8e6f4ogHnbCMUc1CrBY8bkVL106XKXzvYNDTwlCdfYoeZmtKVekQO+Fo0w XC/g== X-Gm-Message-State: AOJu0YxZd9+F2Zv4IYjjwgeeylyfPtIpKdBapX4PNHC/LqlX1NiRg2ua /dQmWQZajU1e7GDx75y0qwLRJhbkUJ/lmyWCBR68TihaR5+4aIvJh5zFVbi7+WmA//aOxIMseof vIT7fzKv7STQcoDP0QTR6lkBrsVemRusp X-Google-Smtp-Source: AGHT+IH/pAUxnfbBsqqR+1MndgqaRygdDsiv96BZF1CPLOBg7lc9gKAY+JX7HZFlZI5y9DlHTPO6yvXLlwSqvDHkPMw= X-Received: by 2002:a2e:9f55:0:b0:2d5:9703:263c with SMTP id v21-20020a2e9f55000000b002d59703263cmr11169899ljk.4.1713375176414; Wed, 17 Apr 2024 10:32:56 -0700 (PDT) MIME-Version: 1.0 References: <72c40850-1dc6-41a9-ba90-e19328999ea8@enterprisedb.com> In-Reply-To: <72c40850-1dc6-41a9-ba90-e19328999ea8@enterprisedb.com> From: Johnathan Tiamoh Date: Wed, 17 Apr 2024 13:32:49 -0400 Message-ID: Subject: Re: Performance degradation after upgrading from 9.5 to 14 To: Tomas Vondra Cc: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000c1e07106164e3ebb" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000c1e07106164e3ebb Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 1) How did you upgrade? pg_dump or pg_upgrade? I use pg_ugrade with kink option. 2) Did you run ANALYZE to collect statistics after the upgrade? Yes. I ran vacuumdb-analyze in stages after the upgrade 3) Did you transfer the configuration, or did you just create a new cluster with the default values? I transfer the configuration 4) What exactly is slower? Queries? Inserts? queries 5) Can you quantify the impact? Is it 2x slower? 100x slower? it's more than 5 times slower than before. Very high load averages On Wed, Apr 17, 2024 at 1:25=E2=80=AFPM Tomas Vondra wrote: > On 4/17/24 19:13, Johnathan Tiamoh wrote: > > Hello, > > > > > > I performed an upgrade from postgresql-9.5 to postgresql-14 and the > > performance has degraded drastically. > > > > Please, is they any advice on getting performance back ? > > > > There's very little practical advice we can provide based on this > report, because it's missing any useful details. There's a number of > things that might have caused this, but we'd have to speculate. > > For example: > > 1) How did you upgrade? pg_dump or pg_upgrade? > > 2) Did you run ANALYZE to collect statistics after the upgrade? > > 3) Did you transfer the configuration, or did you just create a new > cluster with the default values? > > 4) What exactly is slower? Queries? Inserts? > > 5) Can you quantify the impact? Is it 2x slower? 100x slower? > > > regards > > > -- > Tomas Vondra > EnterpriseDB: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > --000000000000c1e07106164e3ebb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
1) How did you upgrade? pg_dump or pg_upgrade?

I use pg_ugrade with kink option.

2) Did you run ANALYZE to = collect statistics after the upgrade?


Yes. I ran vacuumdb-analyze in stages after the upgrade

3) Did yo= u transfer the configuration, or did you just create a new
cluster with = the default values?

I transfer=C2=A0the configurat= ion

4) What exactly is slower? Queries? Inserts?

queries

5) Can you quantify the impact? Is it 2x slower= ? 100x slower?

it's more than 5 times slow= er than before. Very high load averages=C2=A0

On Wed, Apr 17, 2024 at = 1:25=E2=80=AFPM Tomas Vondra <tomas.vondra@enterprisedb.com> wrote:
On 4/17/24 19:13, Johnathan Tiamoh wrot= e:
> Hello,
>
>
> I performed an=C2=A0 upgrade from postgresql-9.5 to postgresql-14 and = the
> performance has degraded drastically.
>
> Please, is they any advice on getting performance back ?
>

There's very little practical advice we can provide based on this
report, because it's missing any useful details. There's a number o= f
things that might have caused this, but we'd have to speculate.

For example:

1) How did you upgrade? pg_dump or pg_upgrade?

2) Did you run ANALYZE to collect statistics after the upgrade?

3) Did you transfer the configuration, or did you just create a new
cluster with the default values?

4) What exactly is slower? Queries? Inserts?

5) Can you quantify the impact? Is it 2x slower? 100x slower?


regards


--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--000000000000c1e07106164e3ebb--