| From: | Fernando Hevia <fhevia(at)gmail(dot)com> |
|---|---|
| To: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
| Cc: | Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Postgres 12 -> 13 any need to re-index? |
| Date: | 2021-02-09 20:12:16 |
| Message-ID: | CAGYT1XRyodtDjhYSQPCZfXA6gXMQKa9W0GPvwD-Z3juw0s588Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
El mar, 9 de feb. de 2021 a la(s) 15:50, Wells Oliver (
wells(dot)oliver(at)gmail(dot)com) escribió:
> 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.
>
>
It didn't rebuild indexes. It scanned rows to update statistics thereby
improving the planner's strategy to execute queries.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | dbatoCloud Solution | 2021-02-10 10:26:36 | function digest(unknown, unknown) does not exist |
| Previous Message | Ron | 2021-02-09 19:19:11 | Re: Postgres 12 -> 13 any need to re-index? |