Re: pg_stop_backup() v2 incorrectly marked as proretset

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: pg_stop_backup() v2 incorrectly marked as proretset
Дата
Msg-id 2976202.1646231744@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  (Aleksander Alekseev <aleksander@timescale.com>)
Re: pg_stop_backup() v2 incorrectly marked as proretset  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Wed, Mar 2, 2022 at 5:25 AM Aleksander Alekseev
> <aleksander@timescale.com> wrote:
>> Declaring a macro inside the procedure body is a bit unconventional.
>> Since it doesn't seem to be used for anything except these two array
>> declarations I suggest keeping simply "3" here.

> I think we do this kind of thing in various places in similar
> situations, and I think it is good style. It makes it easier to catch
> everything if you ever need to update the code.

Yeah, there's plenty of precedent for that coding if you look around.
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.

            regards, tom lane



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: pg_stop_backup() v2 incorrectly marked as proretset
Следующее
От: Aleksander Alekseev
Дата:
Сообщение: Re: pg_stop_backup() v2 incorrectly marked as proretset