From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | gokiburi versus the back branches |
Date: | 2023-02-06 23:27:50 |
Message-ID: | 2930303.1675726070@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I notice that Michael's new BF animal gokiburi is failing in
all the pre-v15 branches, though it's fine in v15 and HEAD.
It's evidently dying from ASLR effects because it's trying
to build with EXEC_BACKEND on Linux: there's lots of
2023-02-06 06:07:02.131 GMT [1503972] FATAL: could not reattach to shared memory (key=813803, addr=0xffff8c3a5000): Invalid argument
2023-02-06 06:07:02.131 GMT [1503971] FATAL: could not reattach to shared memory (key=813803, addr=0xffff8c3a5000): Invalid argument
2023-02-06 06:07:02.132 GMT [1503976] FATAL: could not reattach to shared memory (key=813803, addr=0xffff8c3a5000): Invalid argument
in its logs.
The reason it's okay in v15 and up is presumably this:
Author: Thomas Munro <tmunro(at)postgresql(dot)org>
Branch: master Release: REL_15_BR [f3e78069d] 2022-01-11 00:04:33 +1300
Make EXEC_BACKEND more convenient on Linux and FreeBSD.
Try to disable ASLR when building in EXEC_BACKEND mode, to avoid random
memory mapping failures while testing. For developer use only, no
effect on regular builds.
Is it time to back-patch that commit? The alternative would be
to run the animal with an ASLR-disabling environment variable.
On the whole I think testing that f3e78069d works is more
useful than working around lack of it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2023-02-06 23:35:09 | Re: gokiburi versus the back branches |
Previous Message | Andres Freund | 2023-02-06 22:14:22 | Re: pg_upgrade test failure |