Re: Support for runtime parameters in injection points, for AIO tests
Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.
You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:
docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t51558psql -h localhost -U postgresBuilt from patchset v4 (message #4), July 27, 2026 at 09:13 AM.
Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:
git clone --branch t51558_4 https://github.com/hackorum-dev/postgres.gitIn a checkout you already have, add the fork once:
git remote add hackorum https://github.com/hackorum-dev/postgres.gitthen, for this patchset and every later one:
git fetch hackorum t51558_4 && git checkout t51558_4Patchset v4 (message #4) is on t51558_4
On Thu, May 08, 2025 at 06:16:46PM +0000, Greg Burd wrote:
IMO seems like a good idea, happy to help further "cleanup the AIO
code" with some direction as to what needs to be done.
Thanks for posting a rebase. Yes, I would like to clean up that on
HEAD, but it also seems like Andres would prefer let this matter be
handled once v18 is forked on its own branch, so I am not sure how to
proceed here. Avoiding a diff for this new code between v18 and HEAD
would be nicer, IMO, and we're still in early stability period. And
that would be less conflicts when maintaining these tests across
branches.
Have others an opinion to offer here?
--
Michael
Import Notes
Reply to msg id not found: A85FBDDE-96AE-4789-9376-7F71D4803112@burd.meReference msg id not found: A85FBDDE-96AE-4789-9376-7F71D4803112@burd.me
Hi,
On 2025-05-09 08:19:39 +0900, Michael Paquier wrote:
On Thu, May 08, 2025 at 06:16:46PM +0000, Greg Burd wrote:
IMO seems like a good idea, happy to help further "cleanup the AIO
code" with some direction as to what needs to be done.Thanks for posting a rebase. Yes, I would like to clean up that on
HEAD, but it also seems like Andres would prefer let this matter be
handled once v18 is forked on its own branch, so I am not sure how to
proceed here.
I'm ok with it happening now or only in master after branching off. Either
seems justifiable to me. I really don't have much of an opinion about it - it
seems you do, so we should probably go with that.
Greetings,
Andres
On Thu, May 08, 2025 at 09:18:15PM -0400, Andres Freund wrote:
I'm ok with it happening now or only in master after branching off. Either
seems justifiable to me. I really don't have much of an opinion about it - it
seems you do, so we should probably go with that.
Thanks for the input. Will proceed if there are no objections, then.
--
Michael
On Fri, May 09, 2025 at 10:48:45AM +0900, Michael Paquier wrote:
Thanks for the input. Will proceed if there are no objections, then.
By the way, Greg, v2-0003 in the patch set you have posted was
incorrect; it missed most of the wanted changes to get rid of the
workarounds in the AIO code. Compared to the original version, there
were just two conflicts with the injection point names, nothing huge.
Patch v2 seems to be hold on moderation perhaps? It has not been
published to the lists.
I will not be able to monitor the buildfarm today but I have the
attached v3 staged for commit, for later when I'll be able to do so.
--
Michael
Attachments:
t51558_4v3-0001-Add-support-for-runtime-parameters-in-injection-p.patchtext/x-diff; charset=us-asciiDownload+52-48
v3-0002-injection_points-Add-support-for-runtime-argument.patchtext/x-diff; charset=us-asciiDownload+102-17
v3-0003-aio-Use-runtime-arguments-with-injections-points.patchtext/x-diff; charset=us-asciiDownload+13-85
On Fri, May 09, 2025 at 03:59:48PM +0000, Greg Burd wrote:
Apologies for that, somehow the wrong version of that file was
attached. I'll be more careful next time.
No problem. This was mostly the same as the original. There was a
fuzz in 0001, actually, fixed by 0003 with the definitions of the
callbacks being incorrect.
It would be nice to plant a bit more InjectionPointCallback around
these callback declarations, actually. I'll look into that later.
I have now applied all that and closed the open item, keeping an eye
on the buildfarm in case.
--
Michael
Import Notes
Reply to msg id not found: Q-zqlhNL_MynzmO4LWi9boeI-GAHkPGUbJQBAXShOP9PrCsyPeLjI2VhHmGTkiogbNuUt6Mvc5isqGSfstmW7oYcQKOCk1eJ8B-uQr2J-M8@burd.meReference msg id not found: A85FBDDE-96AE-4789-9376-7F71D4803112@burd.me