Re: Issue with markers in isolation tester? Or not?

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Michail Nikolaev <michail(dot)nikolaev(at)gmail(dot)com>
Cc: Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Issue with markers in isolation tester? Or not?
Date: 2025-01-19 00:59:17
Message-ID: Z4xOZV0VhXyJvZ3d@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jan 18, 2025 at 02:03:33PM +0100, Michail Nikolaev wrote:
> I was able to stabilize (I hope so) tests on [0] without any changes to
> isolationtester and without "notices N".
>
> So, I agree, it is better to put it on a shelf now. But a few words in
> documentation may be a good idea.

Could you summarize here what you have done to achieve test
stabilization in your new patch set posted at [1] without using the
proposal of this thread?

Perhaps that's OK to leave things as they are, but your proposal here
is leading to a more natural definition in terms of how test ordering
can be enforced with injection points, leading to a less confusing
definition. The analysis of existing tests if this proposal moves
forward would be required, of course.

[1]: https://www.postgresql.org/message-id/CANtu0ohStYQkJL+_=40Odcqu2A4QPrM_VmofwkkudHGHFgymkA@mail.gmail.com
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2025-01-19 01:09:11 Re: Pgoutput not capturing the generated columns
Previous Message Michael Paquier 2025-01-19 00:52:14 Re: improve DEBUG1 logging of parallel workers for CREATE INDEX?