Re: Cleaning up threading code
От | Thomas Munro |
---|---|
Тема | Re: Cleaning up threading code |
Дата | |
Msg-id | CA+hUKGJggGdDOdkoJXmrQwHFgY5zYenNod3SKNjGzsiz6+vUdA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Cleaning up threading code (Thomas Munro <thomas.munro@gmail.com>) |
Ответы |
Re: Cleaning up threading code
|
Список | pgsql-hackers |
On Mon, Jul 10, 2023 at 10:45 AM Thomas Munro <thomas.munro@gmail.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. > * defined ENABLE_THREAD_SAFETY 1 ecpg_config.h, for the benefit of ECPG clients I left this one in. I'm not sure if it could really be needed. Perhaps at a stretch, perhaps ECPG code that is statically linked might test that instead of calling PQisthreadsafe(). Pushed.
В списке pgsql-hackers по дате отправления: