miscellaneous pg_upgrade cleanup

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: daniel(at)yesql(dot)se
Subject: miscellaneous pg_upgrade cleanup
Date: 2024-09-17 19:22:21
Message-ID: ZunW7XHLd2uTts4f@nathan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Here are a few miscellaneous cleanup patches for pg_upgrade. I don't think
there's anything controversial here.

0001 removes some extra whitespace in the status message for failed data
type checks. I noticed that when the check fails, this status message is
indented beyond all the other output. This appears to have been introduced
in commit 347758b, so I'd back-patch this one to v17.

0002 improves the coding style in many of the new upgrade task callback
functions. I refrained from adjusting this code too much when converting
these tasks to use the new pg_upgrade task framework (see commit 40e2e5e),
but now I think we should. This decreases the amount of indentation in
some places and removes a few dozen lines of code.

0003 adds names to the UpgradeTaskSlotState enum and the UpgradeTaskSlot
struct. I'm not aware of any established project policy in this area, but
I figured it'd be good to at least be consistent within the same file.

Thoughts?

--
nathan

Attachment Content-Type Size
v1-0001-remove-extra-whitespace-in-pg_upgrade-report.patch text/plain 934 bytes
v1-0002-improve-style-of-upgrade-task-callback-functions.patch text/plain 12.7 KB
v1-0003-add-names-to-some-upgrade-task-structs.patch text/plain 1.0 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2024-09-17 20:16:04 Re: scalability bottlenecks with (many) partitions (and more)
Previous Message David E. Wheeler 2024-09-17 19:16:57 Re: [PATCH] WIP: replace method for jsonpath