Re: Fixes inconsistent behavior in vacuum when it processes multiple relations

shihao zhong <zhong950419@gmail.com>

From: shihao zhong <zhong950419@gmail.com>

To: Michael Paquier <michael@paquier.xyz>

Cc: Nathan Bossart <nathandbossart@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2025-06-20T14:13:38Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Rationalize handling of VacuumParams
- 2252fcd4276c 19 (unreleased) landed
Avoid scribbling of VACUUM options
- 65c3223f93a0 13.22 landed
- c079ba3fc2a4 14.19 landed
- 354944663df3 15.14 landed
- d187cabddadc 16.10 landed
- 2e0b5d252b10 17.6 landed
- 661643dedad9 18.0 landed

Attachments

vacuum_tables_options_4.patch (application/octet-stream) patch

>> However, Option 1) would be my go-to option for HEAD ...

Updated my patch to apply the same rules to all VacuumParams. Also I
am seeing clusterParams as a pass reference, not sure if we should
also change that to prevent future issues. But that should be another
patch.