Re: Postgres 12 -> 13 any need to re-index?

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(at)gmail(dot)com
> <mailto:ronljohnsonjr(at)gmail(dot)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(at)gmail(dot)com
>> <mailto:ronljohnsonjr(at)gmail(dot)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.