From: Konstantin Knizhnik <k.knizhnik@postgrespro.ru>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Memory leak in RelationBuildRowSecurity
Date: Tue, 27 Oct 2020 11:41:43 +0300
Message-ID: <dcf027d5-7603-25b6-6ab1-869e0de97c2a@postgrespro.ru> (raw)
In-Reply-To: <2029358.1601139941@sss.pgh.pa.us>
References: <21356c12-8917-8249-b35f-1c447231922b@postgrespro.ru>
<1852787.1601041699@sss.pgh.pa.us>
<3f670fa6-5e81-fbd9-b880-eaa275f15e1c@postgrespro.ru>
<1937613.1601057234@sss.pgh.pa.us>
<c28d5597-1933-1933-c15c-edadd9186757@postgrespro.ru>
<2029358.1601139941@sss.pgh.pa.us>
On 26.09.2020 20:05, Tom Lane wrote:
> Konstantin Knizhnik <k.knizhnik@postgrespro.ru> writes:
>> On 25.09.2020 21:07, Tom Lane wrote:
>>> This is against HEAD but I think it wouldn't be hard to back-patch.
>>> Are you in a position to see if it fixes the problem in your customer's
>>> environment?
>> Thank you.
>> Your patch fixes the problem.
> Thanks for testing! I'll try to get this committed later today.
>
> regards, tom lane
Just want to convey gratitude from the customer: after apply your patch
memory consumption is decreased 3 times which significantly improves
performance of their system.
--
Konstantin Knizhnik
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: k.knizhnik@postgrespro.ru, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: Re: Memory leak in RelationBuildRowSecurity
In-Reply-To: <dcf027d5-7603-25b6-6ab1-869e0de97c2a@postgrespro.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox