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 1l9XPj-0000Hm-5Z for pgsql-admin@arkaria.postgresql.org; Tue, 09 Feb 2021 18:07:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l9XPh-00036c-R1 for pgsql-admin@arkaria.postgresql.org; Tue, 09 Feb 2021 18:07:01 +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 1l9XPh-00036V-HF for pgsql-admin@lists.postgresql.org; Tue, 09 Feb 2021 18:07:01 +0000 Received: from mail-oo1-xc2b.google.com ([2607:f8b0:4864:20::c2b]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1l9XPf-0001iT-1M for pgsql-admin@lists.postgresql.org; Tue, 09 Feb 2021 18:07:00 +0000 Received: by mail-oo1-xc2b.google.com with SMTP id y21so4454214oot.12 for ; Tue, 09 Feb 2021 10:06:58 -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-transfer-encoding:content-language; bh=nVhu1sAywiB6K0K4NZj89KQ5F8sSdtgu779wHaD79IA=; b=gSSbcEBKInv3GvYZpCp4fkk0V9wNM+IXEc/VMkZ1XSU4T5AQV8bJUShlAWSPis0waD uCvTDe7PkznOLAWGMKmZe6NGuXrayWioFnI7r0uDA6ugeQhMnKOJwVolUCnY5LtQY2lz v2bv9uatgstuSf0dc6jsb/r+IR6moCjquPM7Eg1bzFI5yyxxU0babfTyeCHU2OunrErl sASOSauBWOakqqfHYl193d7yVcYLbxVTxbC4qVSjFnkC1+/wV3fXve/WDkbGJoLeR2Ux T9kBcDKhRchCA6S7gm2OTcF+OWitcJ1Kv1k0M9mYo0xb5ezmPIPMawUluHQoeEvqsmu/ Z5kg== 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-transfer-encoding :content-language; bh=nVhu1sAywiB6K0K4NZj89KQ5F8sSdtgu779wHaD79IA=; b=o4wHFEnHm31MYgqIA4ZgbX2crnR7ocJVKS5tN3fbBflmYSiTyXUYUaG5lrBOjAyRZF 6tb5yB0ipQw+/YrpsJaPutZM0bwwQNfzkQs/B03xESvnDgqiKaAOrBkVctcB1g9AbwK7 ys2gu8AVhrt0Io0HsFrZ9ZIiWVgkSBIj2/DCO9Pd7fRenWqy6DS5J0LetJjOe34herYn 6ltQNzzQrWyJAJH67Y5WF83KttrzodOSNiZTkx3yKuTOdiIbKJpd9nM7mmCaB0AO9L7I DnBlsiWys6ad2SbBdW/zVvb9LsYjHHajWV4eO5UrOnQ58CAfrdPja1JZPgqsZJpT8dH4 /SnQ== X-Gm-Message-State: AOAM531ePz+dBdY99AHG0OE4EqeW5wSP3YEC8oVnKPhjri0j8xls6Ar7 a57jwTbalU34GYBfgPJl+ekT3t3smk6f2g== X-Google-Smtp-Source: ABdhPJzna7SxWgBb/KZ0exQErmLWAsZXUsTstM2emAeh1qc8BVx9nnDaAPNRxL76PVcFI7Q0L/p39A== X-Received: by 2002:a4a:c602:: with SMTP id l2mr16677783ooq.5.1612894016774; Tue, 09 Feb 2021 10:06:56 -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 m10sm4499151oim.42.2021.02.09.10.06.55 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 09 Feb 2021 10:06:55 -0800 (PST) Subject: Re: Postgres 12 -> 13 any need to re-index? To: pgsql-admin@lists.postgresql.org References: From: Ron Message-ID: <8f24ff9a-059e-ee95-38bf-07e5b852d226@gmail.com> Date: Tue, 9 Feb 2021 12:06:55 -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: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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.