From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Cleaning up threading code |
Date: | 2023-07-11 22:49:53 |
Message-ID: | 20230711224953.abfpupu3lrrgyiqw@awork3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2023-07-12 08:58:29 +1200, Thomas Munro wrote:
> On Mon, Jul 10, 2023 at 10:45 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> > * defined ENABLE_THREAD_SAFETY 1 in c.h, for the benefit of extensions
>
> I may lack imagination but I couldn't think of any use for that
> vestigial macro in backend/extension code, and client code doesn't see
> c.h and might not get the right answer anyway if it's dynamically
> linked which is the usual case. I took it out for now. Open to
> discussing further if someone can show what kinds of realistic
> external code would be affected.
WFM.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2023-07-11 23:29:42 | Re: Support to define custom wait events for extensions |
Previous Message | Ranier Vilela | 2023-07-11 22:46:16 | Re: Avoid unused value (src/fe_utils/print.c) |