Re: Weird test mixup

From: "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Weird test mixup
Date: 2024-04-06 05:34:46
Message-ID: FB71B3B1-D68F-4508-BA95-D427792FAB2B@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 5 Apr 2024, at 07:19, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> It's been a couple of weeks since this has been sent, and this did not
> get any reviews. I'd still be happy with the simplicity of a single
> injection_points_local() that can be used to link all the injection
> points created in a single process to it, discarding them once the
> process exists with a shmem exit callback.

OK, makes sense.
I find name of the function "injection_points_local()" strange, because there is no verb in the name. How about "injection_points_set_local"?

> And I don't really see an
> argument to tweak the backend-side routines, as well.
> Comments and/or
> objections?

I'm not sure if we should refactor anything here, but InjectionPointSharedState has singular name, plural wait_counts and singular condition.
InjectionPointSharedState is already an array of injection points, maybe let's add there optional pid instead of inventing separate array of pids?

Can we set global point to 'notice', but same local to 'wait'? Looks like now we can't, but allowing to do so would make code simpler.

Besides this opportunity to simplify stuff, both patches looks good to me.

Best regards, Andrey Borodin.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2024-04-06 06:02:23 Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?
Previous Message Amit Kapila 2024-04-06 05:28:32 Re: Synchronizing slots from primary to standby