Re: Lots of memory allocated when reassigning Large Objects - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Lots of memory allocated when reassigning Large Objects
Date
Msg-id 1534526.1638228309@sss.pgh.pa.us
Whole thread Raw
In response to Re: Lots of memory allocated when reassigning Large Objects  (Guillaume Lelarge <guillaume@lelarge.info>)
Responses Re: Lots of memory allocated when reassigning Large Objects
List pgsql-hackers
Guillaume Lelarge <guillaume@lelarge.info> writes:
> Le lun. 29 nov. 2021 à 22:27, Tom Lane <tgl@sss.pgh.pa.us> a écrit :
>> I'm checking it in HEAD though; perhaps there's something else wrong
>> in the back branches?

> That's also what I was thinking. I was only trying with v14. I just checked
> with v15devel, and your patch works alright. So there must be something
> else with back branches.

AFAICT the patch fixes what it intends to fix in v14 too.  The reason the
residual leak is worse in v14 is that the sinval message queue is bulkier.
We improved that in HEAD in commit 3aafc030a.  I'm not sure if I want to
take the risk of back-patching that, even now that it's aged a couple
months in the tree.  It is a pretty localized fix, but it makes some
assumptions about usage patterns that might not hold up.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: SSL Tests for sslinfo extension
Next
From: Greg Nancarrow
Date:
Subject: Re: Correct handling of blank/commented lines in PSQL interactive-mode history