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 1l9Xhc-0000r2-4i for pgsql-admin@arkaria.postgresql.org; Tue, 09 Feb 2021 18:25:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l9XhZ-0000wU-No for pgsql-admin@arkaria.postgresql.org; Tue, 09 Feb 2021 18:25:29 +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 1l9XhZ-0000wM-CS for pgsql-admin@lists.postgresql.org; Tue, 09 Feb 2021 18:25:29 +0000 Received: from mail-oi1-x22f.google.com ([2607:f8b0:4864:20::22f]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1l9XhW-0001rp-7w for pgsql-admin@lists.postgresql.org; Tue, 09 Feb 2021 18:25:28 +0000 Received: by mail-oi1-x22f.google.com with SMTP id g84so6647340oib.0 for ; Tue, 09 Feb 2021 10:25:25 -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=GFxKhvkchGQ9X7pkwxrFXDnYgkJMg7pMQMrif9cV20I=; b=fuZ40+d14uJkOywIr5nRAfVDF/clkeplS4LHZiwJYEwpu28KEjRAJZulEEg1IgHOdn Boq2XXMPJHpcnGekOjMimqcjOEYRrgF3KQQn6/IWOGFdR7sU7kgA6YvkFOg/XCGcheTg ZOz/NdxpHaMOYRqPWaXdEkfnZB9bmF1oRRboPfpYoZFpwShCMZ/oXkNF+72gm5aLk32B qcfab8flD7b4defitrRAVDwptTOIPXSnnJRROJCc+gCw4bO1JG33CzOrjbNEMJwUhT0L 0qdDXBwAsTaZVbm8fL0S74XsUyV5U3ygxCdxxOZV3xz3n2FJTe5jyjvyRVwcfpONm7Rj v6qQ== 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=GFxKhvkchGQ9X7pkwxrFXDnYgkJMg7pMQMrif9cV20I=; b=oO7C2JHrpaB2VnMLPDRTC98lBsAwLagzxGd55G0VAtyGZ/iXpZxr4rDtGON6xEmpa6 OwDjqzUCpVZSb3z1m/TOcJi7yastCgU7pB0H3xNnlgt9CMY800DsXBvuyVkQScdxTy/0 ZwSwWPSP2RnWzf3bXnI3bOUSL65O+mYXRZtp08CkagwAQxVcTByWkEtbSBbYrk7MKKBk asnGXJEaERUZvWxfTn3ZfhaekTRB5KfonVY9z+sBPBzGnSZMdp3jFa8QnqDGarVTIqQc dcRNQeynsGbPRoZiqlWD0jEGo2jBYYNOKZJTSHkJQNYIrPJK/eZuGlmIUNKn09K1ssWQ dP2w== X-Gm-Message-State: AOAM5303ufWw9EeRIOzy99tHdND1sg1Bwg3WvMhVFQ1OJFuR0e3bNRXq 6kFcCurUml6MgHaXqzCWWb4M3Y5TnmVc/w== X-Google-Smtp-Source: ABdhPJyLnkih7yOyB45wa8Dik/Zk9xg8b9SxnOI6cO/Nnh099weJdccWRTHehB3uvGVUoUXjL0nP+g== X-Received: by 2002:a54:4e87:: with SMTP id c7mr3345846oiy.94.1612895123673; Tue, 09 Feb 2021 10:25:23 -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 m22sm4313290ooj.43.2021.02.09.10.25.22 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 09 Feb 2021 10:25:23 -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> <4c1d3278-b5cc-c432-c2c5-12b3c453ab79@gmail.com> From: Ron Message-ID: <5cdc65bb-a095-a161-06d6-cfd73faeaf3b@gmail.com> Date: Tue, 9 Feb 2021 12:25:22 -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="------------D431EC5FE87800FA2444CD31" 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. --------------D431EC5FE87800FA2444CD31 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit On 2/9/21 12:18 PM, Wells Oliver wrote: > No, I didn't. I had done that in testing Tsk tsk. > and wanted to get the thing back up and running. Would i just run 'analyze > dbname' or something more verbose? Essentially.  I'd do something like: vacuumdb --analyze-only --jobs=$(nproc) -d ${YOUR_DB} > > On Tue, Feb 9, 2021 at 10:17 AM Ron > wrote: > > 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. --------------D431EC5FE87800FA2444CD31 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit On 2/9/21 12:18 PM, Wells Oliver wrote:
No, I didn't. I had done that in testing

Tsk tsk.

and wanted to get the thing back up and running. Would i just run 'analyze dbname' or something more verbose?

Essentially.  I'd do something like:

vacuumdb --analyze-only --jobs=$(nproc) -d ${YOUR_DB}


On Tue, Feb 9, 2021 at 10:17 AM Ron <ronljohnsonjr@gmail.com> wrote:
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.
--------------D431EC5FE87800FA2444CD31--