Re: Decoding speculative insert with toast leaks memory

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Decoding speculative insert with toast leaks memory
Дата
Msg-id YNQZRz4G9HjNbVfh@paquier.xyz
обсуждение исходный текст
Ответ на Re: Decoding speculative insert with toast leaks memory  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Decoding speculative insert with toast leaks memory  (Amit Kapila <amit.kapila16@gmail.com>)
Список pgsql-hackers
On Thu, Jun 24, 2021 at 12:25:15AM -0400, Tom Lane wrote:
> Amit Kapila <amit.kapila16@gmail.com> writes:
>> Okay, I'll change this in back branches and HEAD to keep the code
>> consistent, or do you think it is better to retain the order in HEAD
>> as it is and just change it for back-branches?
>
> As I said, I'd keep the natural ordering in HEAD.

Yes, please keep the items in an alphabetical order on HEAD, and just
have the new item at the bottom of the enum in the back-branches.
That's the usual practice.
--
Michael

Вложения

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Decoding speculative insert with toast leaks memory
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: [PATCH] Make jsonapi usable from libpq