From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Postgres 12 -> 13 any need to re-index?
Date: Tue, 9 Feb 2021 13:19:11 -0600
Message-ID: <b9aa1d34-2b57-5862-8848-0c3620bfa57a@gmail.com> (raw)
In-Reply-To: <CAOC+FBVypXXXeH_5BjNbuiZWyFJNzkrsQg86uSSGSfV=7fRbDw@mail.gmail.com>
References: <CAOC+FBVK9UU4xVHkVkJsETGeux=girhDH=M5mZFjN454c58U3A@mail.gmail.com>
<8f24ff9a-059e-ee95-38bf-07e5b852d226@gmail.com>
<CAOC+FBXpgqJ9xR2z85JdU58beWKWmz88a=bFx4SK7bu-cH=1+A@mail.gmail.com>
<4c1d3278-b5cc-c432-c2c5-12b3c453ab79@gmail.com>
<CAOC+FBVK3y4Dev1+Q50OQf4hS8z5FgKvWVZLE5Do=7Cr3YT9AA@mail.gmail.com>
<5cdc65bb-a095-a161-06d6-cfd73faeaf3b@gmail.com>
<CAOC+FBUL9od=NHH7_26k2=aYdUzFJLgVfsLT4+WCRzAFihgDYg@mail.gmail.com>
<CAOC+FBVypXXXeH_5BjNbuiZWyFJNzkrsQg86uSSGSfV=7fRbDw@mail.gmail.com>
This command is well documented:
vacuumdb --analyze-only --jobs=$(nproc) -d ${YOUR_DB}
On 2/9/21 12:49 PM, Wells Oliver wrote:
> OK, that seems to have made a huge difference. and ran very quickly, ~15
> mins on a ~1TB database. Is there a way to better understand what it did?
> There's no way it rebuilt indexes in that amount of time. Also, as I said,
> I never did that going from 9->10->11->12, so it's interesting to me that
> it was so critical this time around.
>
>
>
> On Tue, Feb 9, 2021 at 10:27 AM Wells Oliver <wells.oliver@gmail.com
> <mailto:wells.oliver@gmail.com>> wrote:
>
> Yeah. Running that now. Honestly, I went from 9 to 10 to 11 to 12
> without doing that in prod, and it was marvelous. 13 hit a wall, and
> I'm not sure why.
>
> It's running now, though...
>
> On Tue, Feb 9, 2021 at 10:25 AM Ron <ronljohnsonjr@gmail.com
> <mailto:ronljohnsonjr@gmail.com>> wrote:
>
> 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
>> <mailto: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
>>> <mailto: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.
>
>
>
> --
> Wells Oliver
> wells.oliver@gmail.com <mailto:wellsoliver@gmail.com>
>
>
>
> --
> Wells Oliver
> wells.oliver@gmail.com <mailto:wellsoliver@gmail.com>
--
Angular momentum makes the world go 'round.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Postgres 12 -> 13 any need to re-index?
In-Reply-To: <b9aa1d34-2b57-5862-8848-0c3620bfa57a@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox