Re: Lots of memory allocated when reassigning Large Objects

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Lots of memory allocated when reassigning Large Objects
Date: 2021-11-29 23:25:09
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Guillaume Lelarge <guillaume(at)lelarge(dot)info> writes:
> Le lun. 29 nov. 2021 à 22:27, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Nancarrow 2021-11-29 23:37:42 Re: Correct handling of blank/commented lines in PSQL interactive-mode history
Previous Message Daniel Gustafsson 2021-11-29 23:16:57 Re: SSL Tests for sslinfo extension