| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Jeff Davis <jdavis(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Trial fix for old cross-version upgrades. |
| Date: | 2025-02-22 03:11:06 |
| Message-ID: | 3892121.1740193866@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Jeff Davis <pgsql(at)j-davis(dot)com> writes:
> In 002_pg_upgrade.pl, I disabled autovacuum and restarted after the
> regression run. In other words, in the old cluster, autovacuum did have
> a chance to run, just not after the first dumpall.
The hack I posted should prevent autovacuum from running either
before or after dumping, in either cluster.
However, it occurred to me to try forcing a HEAD-to-HEAD upgrade,
a case the buildfarm animals have not been able to reach.
And *it failed*!? (Diffs attached.) So that eliminates the
theory that this is a cross-version compatibility problem, or
at least that is not our only problem. It seems there is
something different between what TestUpgradeXversion.pm is doing
and what 002_pg_upgrade.pl is doing. No clue what, although it
does look like an additional round of analyze'ing has added more
stats than were there before.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| dumpdiff-HEAD | text/x-diff | 1.4 MB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2025-02-22 06:21:04 | pgsql: Remove unstable test suite added by 525392d57 |
| Previous Message | Jeff Davis | 2025-02-22 03:00:07 | Re: pgsql: Trial fix for old cross-version upgrades. |