public inbox for [email protected]
help / color / mirror / Atom feedFrom: Michael Paquier <[email protected]>
To: shihao zhong <[email protected]>
Cc: Nathan Bossart <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: Fixes inconsistent behavior in vacuum when it processes multiple relations
Date: Thu, 26 Jun 2025 07:47:22 +0900
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAGRkXqStMeemxvmTKxKxb5eD+pWNnLLDYGe1qOEF9EwKh+Gp_A@mail.gmail.com>
References: <aFRzYhOTZcRgKPLu@nathan>
<[email protected]>
<aFWznvZtYZ3VJxgi@nathan>
<[email protected]>
<aFl1AB9ofnQrrckV@nathan>
<[email protected]>
<aFrSlSz9fi47j5Sr@nathan>
<[email protected]>
<aFwT31Rw-Oj-bgO9@nathan>
<CAGRkXqStMeemxvmTKxKxb5eD+pWNnLLDYGe1qOEF9EwKh+Gp_A@mail.gmail.com>
On Wed, Jun 25, 2025 at 01:12:02PM -0400, shihao zhong wrote:
> Just want to make sure, are we not going to include my original test
> to catch the future regression? Also, could someone please let me know
> how to check if the test is stable or not?
On stable branches, you could reuse the patch I have posted upthread,
even if it is not included in the tree. On HEAD and v17, you can run
the tests of src/test/modules/injection_points/ with
--enable-injection-points set.
Making the index cleanup stable takes a certain amount of cycles
because it requires a minimum amount of data, particularly for the
btree of a TOAST index. The truncation check is halfly stable: it is
possible to check that a truncation does not happen, but it can still
be slightly unstable because the option may not trigger all the time.
So, while the test success rate is perhaps close to 90%, with this
rate going down on slower machines, it is just cheaper and more
reliable to check directly the contents of VacuumParams. Note that
your original set of tests only covered the case of multiple
relations, and it missed coverage for the TOAST relation vacuumed
after its main relation.
--
Michael
Attachments:
[application/pgp-signature] signature.asc (833B, 2-signature.asc)
download
view thread (32+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Fixes inconsistent behavior in vacuum when it processes multiple relations
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox