Re: Decoding speculative insert with toast leaks memory

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Decoding speculative insert with toast leaks memory
Дата
Msg-id 2569713.1624508715@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Decoding speculative insert with toast leaks memory  (Amit Kapila <amit.kapila16@gmail.com>)
Ответы Re: Decoding speculative insert with toast leaks memory  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers
Дерево обсуждения 
Amit Kapila <amit.kapila16@gmail.com> writes:
>> I think it's OK in HEAD.  I agree we shouldn't do it like that
>> in the back branches.

> 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.

            regards, tom lane

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

Предыдущее
От: "houzj.fnst@fujitsu.com"
Дата:
Сообщение: RE: [bug?] Missed parallel safety checks, and wrong parallel safety
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: Decoding speculative insert with toast leaks memory