Re: pg_stop_backup() v2 incorrectly marked as proretset
От
Tom Lane
Тема
Re: pg_stop_backup() v2 incorrectly marked as proretset
Дата
Msg-id
3441490.1646343642@sss.pgh.pa.us
Ответ на
Re: pg_stop_backup() v2 incorrectly marked as proretset (Robert Haas)
Список
Дерево обсуждения
pg_stop_backup() v2 incorrectly marked as proretset Michael Paquier <michael@paquier.xyz>
Re: pg_stop_backup() v2 incorrectly marked as proretset Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Re: pg_stop_backup() v2 incorrectly marked as proretset Michael Paquier <michael@paquier.xyz>
Re: pg_stop_backup() v2 incorrectly marked as proretset Aleksander Alekseev <aleksander@timescale.com>
Re: pg_stop_backup() v2 incorrectly marked as proretset Robert Haas <robertmhaas@gmail.com>
Re: pg_stop_backup() v2 incorrectly marked as proretset Tom Lane <tgl@sss.pgh.pa.us>
Re: pg_stop_backup() v2 incorrectly marked as proretset Robert Haas <robertmhaas@gmail.com>
Re: pg_stop_backup() v2 incorrectly marked as proretset Tom Lane <tgl@sss.pgh.pa.us>
Re: pg_stop_backup() v2 incorrectly marked as proretset Chapman Flack <chap@anastigmatix.net>
Re: pg_stop_backup() v2 incorrectly marked as proretset Tom Lane <tgl@sss.pgh.pa.us>
Re: pg_stop_backup() v2 incorrectly marked as proretset Michael Paquier <michael@paquier.xyz>
Re: pg_stop_backup() v2 incorrectly marked as proretset Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Re: pg_stop_backup() v2 incorrectly marked as proretset Aleksander Alekseev <aleksander@timescale.com>
Re: pg_stop_backup() v2 incorrectly marked as proretset Julien Rouhaud <rjuju123@gmail.com>
Re: pg_stop_backup() v2 incorrectly marked as proretset Michael Paquier <michael@paquier.xyz>
Re: pg_stop_backup() v2 incorrectly marked as proretset Chapman Flack <chap@anastigmatix.net>
Re: pg_stop_backup() v2 incorrectly marked as proretset David Steele <david@pgmasters.net>
Re: pg_stop_backup() v2 incorrectly marked as proretset Michael Paquier <michael@paquier.xyz>
Robert Haas writes: > On Wed, Mar 2, 2022 at 9:35 AM Tom Lane wrote: >> I've not read the whole patch, but this snippet seems fine to me >> if there's also an #undef at the end of the function. >> From later emails, it sounds like that's not the common practice in > similar cases, and I don't personally see the point. The point is to make it clear that the macro isn't intended to affect code outside the function. Since C lacks block-scoped macros, there's no other way to do that. I concede that a lot of our code is pretty sloppy about this, but that doesn't make it a good practice. regards, tom lane
В списке pgsql-hackers по дате отправления
От: Zhihong Yu
Дата: