| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Christoph Berg <myon(at)debian(dot)org> |
| Cc: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Update guidance for running vacuumdb after pg_upgrade. |
| Date: | 2025-04-22 21:29:21 |
| Message-ID: | aAgKMavWTlgjWkar@nathan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Tue, Apr 22, 2025 at 11:03:29PM +0200, Christoph Berg wrote:
> Re: Nathan Bossart
>> In any case, IMO it's unfortunate
>> that we might end up recommending roughly the same post-upgrade steps as
>> before even though the optimizer statistics are carried over.
>
> Maybe the docs (and the pg_upgrade scripts) should recommend the old
> procedure by default until this gap is closed? People could then still
> opt to use the new procedure in specific cases.
I think we'd still want to modify the --analyze-in-stages recommendation
(from what is currently recommended for supported versions). If we don't,
you'll wipe out the optimizer stats you brought over from the old version.
Here is a rough draft of what I am thinking.
--
nathan
| Attachment | Content-Type | Size |
|---|---|---|
| post_upgrade_guidance.patch | text/plain | 2.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-04-23 04:55:21 | pgsql: Remove assertion based on pending_since in pgstat_report_stat() |
| Previous Message | Christoph Berg | 2025-04-22 21:03:29 | Re: pgsql: Update guidance for running vacuumdb after pg_upgrade. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Berg | 2025-04-22 21:39:34 | Re: What's our minimum supported Python version? |
| Previous Message | Ivan Kush | 2025-04-22 21:29:10 | Re: [PoC] Federated Authn/z with OAUTHBEARER |