From: | Noah Misch <noah(at)leadboat(dot)com> |
---|---|
To: | Michail Nikolaev <michail(dot)nikolaev(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Issue with markers in isolation tester? Or not? |
Date: | 2025-01-14 04:03:00 |
Message-ID: | 20250114040300.90.nmisch@google.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jan 13, 2025 at 02:02:00AM +0100, Michail Nikolaev wrote:
> While stabilizing tests for [0] I have noticed unclear (and confusing in my
> opinion) behavior of markers in the isolation tester.
>
> I have attached a test with reproducer.
>
> There are two permutations in the test:
>
> permutation
> after(before)
> before
> detach1
> wakeup1
> detach2
> wakeup2
>
> In that case, I see expected results:
> step before: <... completed>
> step after: <... completed>
>
> But changing the order of steps slightly:
>
> permutation
> after(before)
> wakeup1 <------- wakeup moved here
> before
> detach1
> detach2
> wakeup2
>
> makes "after" to be completed before "before". Does that make sense?
Yes. I don't see a good reason for isolationtester to disregard that
"(before)" marker, so I think you've found a bug in isolationtester. How
might we fix it?
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2025-01-14 04:39:07 | Re: Conflict detection for update_deleted in logical replication |
Previous Message | Michael Paquier | 2025-01-14 03:54:36 | Re: WAL-logging facility for pgstats kinds |