Re: pg_stop_backup() v2 incorrectly marked as proretset

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: pg_stop_backup() v2 incorrectly marked as proretset
Дата
Msg-id CA+TgmoYyhGc_cxk8gqN=bi4+3sDeqzfEgxwSjzvVQ9xVsS1T=w@mail.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  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Wed, Mar 2, 2022 at 9:35 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 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.

From later emails, it sounds like that's not the common practice in
similar cases, and I don't personally see the point.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: [Proposal] Global temporary tables
Следующее
От: Andres Freund
Дата:
Сообщение: Re: casting operand to proper type in BlockIdGetBlockNumber