Postgres Pro
Downloads
Home   >   mailing lists

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

From Michael Paquier
Subject Re: Decoding speculative insert with toast leaks memory
Date
Msg-id YNQZRz4G9HjNbVfh@paquier.xyz
Whole thread Raw
In response to Re: Decoding speculative insert with toast leaks memory  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Decoding speculative insert with toast leaks memory
List pgsql-hackers
Tree view 
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
Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Decoding speculative insert with toast leaks memory
Next
From: Michael Paquier
Date:
Subject: Re: [PATCH] Make jsonapi usable from libpq