Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l9XZn-0000Yn-JR for pgsql-admin@arkaria.postgresql.org; Tue, 09 Feb 2021 18:17:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l9XZm-0003ML-HX for pgsql-admin@arkaria.postgresql.org; Tue, 09 Feb 2021 18:17:26 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l9XZm-0003MD-A3 for pgsql-admin@lists.postgresql.org; Tue, 09 Feb 2021 18:17:26 +0000 Received: from mail-ot1-x32d.google.com ([2607:f8b0:4864:20::32d]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1l9XZk-0001oG-AA for pgsql-admin@lists.postgresql.org; Tue, 09 Feb 2021 18:17:25 +0000 Received: by mail-ot1-x32d.google.com with SMTP id l23so6685204otn.10 for ; Tue, 09 Feb 2021 10:17:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=JpB3DWpguhZ6On2aAqlZG49tUvnkGRaXQiWrVBryhdM=; b=d28V6uFbkkc2q4ey0rBWcnwGBoWo3DCIJlnb9PGAjkdXcUVKuT+jEND4cf9i5Hbe60 ONX39Cb2JXbqkQmJHH6PtkMmNY6nxWCeWLjHrvDXnjfpGkny6cdnjWHgDBdFsdftSuto 7BeYzGHuCXZB5Pk9HbetAl5AbYLLkRcMlG/8eqEs8PWDM0YJEa+eY7/US35h5531fZr+ 5SnTfcEmL/0vmAKVD5stu+GKRQ/d7GLkRjoo5eRPfa771rUEfin9QB9TuFDhcEcQG2Ed qN14slp0Z8spiqj7HSfG0ZQjCSXUPDuJK4tPgHMo5Ld7WuiYoOtEpyssOh/7UW8do1yA Gdvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=JpB3DWpguhZ6On2aAqlZG49tUvnkGRaXQiWrVBryhdM=; b=grh6umEJ492q38cz2Ei38uALnKGT/FuPffPtBX/PiAaWxJSddDNhGKE+wnTeD0kP4b bqNdksPsDLfYLhlM8OK3myVmlebLlGY/UHXOE/aseGpMqc790OozFNq2949NSq/9Lt5g zU1YKc9cykK8zY1tnd9Oo7Q/6Q0OAWLHhY/DWbSzzSzI+hLUBioxZdMjvkPQ91G3EhSY CqeznD7hiif9c38WeRv3tDq9PTlriju9+/CxMDjEJQYW3iiZhoXf8zJnNjWwfsIy5QuP 42S0GLNa9MANrxFyOw+X63FB/gQXlfFAriQbmjoW7MpYjWnOzIhFc6odrdwzX+WsxljN 3Tyw== X-Gm-Message-State: AOAM530PS0FTIFgrJvVPNNffVxX899RziFc2pvAw4rFek82huHeq6+85 xfKfFn6YExVTL+lJodI2ZGr4j+yiynNO5Q== X-Google-Smtp-Source: ABdhPJxWyo3byYgeVefLgKILMuQPLKyljR66rzQFCJPYXRuRN3t1bvL9oI/E4Gxsi2uzfLmIXuHFlA== X-Received: by 2002:a9d:3d87:: with SMTP id l7mr16053482otc.317.1612894642109; Tue, 09 Feb 2021 10:17:22 -0800 (PST) Received: from [192.168.88.10] (ip174-67-141-204.no.no.cox.net. [174.67.141.204]) by smtp.googlemail.com with ESMTPSA id y5sm2024129oti.59.2021.02.09.10.17.21 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 09 Feb 2021 10:17:21 -0800 (PST) Subject: Re: Postgres 12 -> 13 any need to re-index? To: pgsql-admin@lists.postgresql.org References: <8f24ff9a-059e-ee95-38bf-07e5b852d226@gmail.com> From: Ron Message-ID: <4c1d3278-b5cc-c432-c2c5-12b3c453ab79@gmail.com> Date: Tue, 9 Feb 2021 12:17:20 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------4EAE94A18B6FA2B12414213D" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------4EAE94A18B6FA2B12414213D Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 2/9/21 12:13 PM, Wells Oliver wrote: > Do you mean Ubuntu distro? I did not. My database collation is also still > en_US.UTF-8, but everything has ground to a halt after the upgrade. Did you run an ANALYZE after the conversion? > > On Tue, Feb 9, 2021 at 10:07 AM Ron > wrote: > > On 2/9/21 12:00 PM, Wells Oliver wrote: > > Hey guys, I just upgraded a DB from 12 to 13. In testing this seemed > to go > > well, but it seems like most of my queries are not using the indexes > after > > the upgrade, so everything is quite so. > > > > Is there a general need to REINDEX after upgrading to 13, or might > there > > be another issue? The configuration parameters are the same as they > were > > persisted via pg_upgradecluster. > > Did you also change or upgrade the distro, or modify the collation? > (That's > an automatic need to rebuild indices.) > -- Angular momentum makes the world go 'round. --------------4EAE94A18B6FA2B12414213D Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit On 2/9/21 12:13 PM, Wells Oliver wrote:
Do you mean Ubuntu distro? I did not. My database collation is also still en_US.UTF-8, but everything has ground to a halt after the upgrade.

Did you run an ANALYZE after the conversion?


On Tue, Feb 9, 2021 at 10:07 AM Ron <ronljohnsonjr@gmail.com> wrote:
On 2/9/21 12:00 PM, Wells Oliver wrote:
> Hey guys, I just upgraded a DB from 12 to 13. In testing this seemed to go
> well, but it seems like most of my queries are not using the indexes after
> the upgrade, so everything is quite so.
>
> Is there a general need to REINDEX after upgrading to 13, or might there
> be another issue? The configuration parameters are the same as they were
> persisted via pg_upgradecluster.

Did you also change or upgrade the distro, or modify the collation? (That's
an automatic need to rebuild indices.)

--
Angular momentum makes the world go 'round.
--------------4EAE94A18B6FA2B12414213D--