Postgres Pro
Downloads
Home   >   mailing lists

Re: Decoding speculative insert with toast leaks memory - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Decoding speculative insert with toast leaks memory
Date
Msg-id 2569713.1624508715@sss.pgh.pa.us
Whole thread Raw
In response to Re: Decoding speculative insert with toast leaks memory  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Decoding speculative insert with toast leaks memory  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Tree view 
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 by date:

Previous
From: "houzj.fnst@fujitsu.com"
Date:
Subject: RE: [bug?] Missed parallel safety checks, and wrong parallel safety
Next
From: Michael Paquier
Date:
Subject: Re: Decoding speculative insert with toast leaks memory