Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kMDeO-00076R-7L for pgsql-bugs@arkaria.postgresql.org; Sat, 26 Sep 2020 17:06:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kMDdr-0001be-Fo for pgsql-bugs@arkaria.postgresql.org; Sat, 26 Sep 2020 17:05:47 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kMDdr-0001bW-9W for pgsql-bugs@lists.postgresql.org; Sat, 26 Sep 2020 17:05:47 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kMDdo-0005zz-H1 for pgsql-bugs@lists.postgresql.org; Sat, 26 Sep 2020 17:05:46 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 08QH5fLm2029359; Sat, 26 Sep 2020 13:05:41 -0400 From: Tom Lane To: Konstantin Knizhnik cc: pgsql-bugs@lists.postgresql.org Subject: Re: Memory leak in RelationBuildRowSecurity In-reply-to: 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> Comments: In-reply-to Konstantin Knizhnik message dated "Sat, 26 Sep 2020 19:37:45 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2029357.1601139941.1@sss.pgh.pa.us> Date: Sat, 26 Sep 2020 13:05:41 -0400 Message-ID: <2029358.1601139941@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Konstantin Knizhnik 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