Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sbIA4-00FU6h-Nn for pgsql-bugs@arkaria.postgresql.org; Tue, 06 Aug 2024 11:15:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sbIA2-00EGlh-VL for pgsql-bugs@arkaria.postgresql.org; Tue, 06 Aug 2024 11:15:26 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sbIA2-00EGlA-Jo for pgsql-bugs@lists.postgresql.org; Tue, 06 Aug 2024 11:15:26 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sbIA0-003S8u-EA for pgsql-bugs@lists.postgresql.org; Tue, 06 Aug 2024 11:15:25 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 4E59370845 for ; Tue, 06 Aug 2024 13:15:23 +0200 (CEST) Received: from s981.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id 3951D700B8; Tue, 06 Aug 2024 13:15:23 +0200 (CEST) Received: from s474.loopia.se (unknown [172.22.191.6]) by s981.loopia.se (Postfix) with ESMTP id 37F0622B17AF; Tue, 06 Aug 2024 13:15:23 +0200 (CEST) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.2 X-Spam-Level: X-Spam-Status: No, score=-1.2 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1] autolearn=disabled Authentication-Results: s474.loopia.se (amavisd-new); dkim=pass (2048-bit key) header.d=yesql.se Received: from s980.loopia.se ([172.22.191.5]) by s474.loopia.se (s474.loopia.se [172.22.190.14]) (amavisd-new, port 10024) with LMTP id 5RrIQ0Av1LRH; Tue, 6 Aug 2024 13:15:22 +0200 (CEST) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.193 Received: from smtpclient.apple (customer-89-255-232-193.stosn.net [89.255.232.193]) (Authenticated sender: daniel@yesql.se) by s980.loopia.se (Postfix) with ESMTPSA id 9158B22015E2; Tue, 06 Aug 2024 13:15:22 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yesql.se; s=loopiadkim1707475645; t=1722942922; bh=jWeDyRbQoq4By5lDfBuULhYtor6W4bDryJVSLPiGTRE=; h=From:Subject:Date:References:To:In-Reply-To; b=NqNo0jxZixnBty0xp1QXt/fnZZOjtd3YHkbezdeSuhRIKD7u2Vc39ZfLyQhcQWOEk 9CuwN2ewut+laFAN5pcz3x/buBxy7KpOH150xKBTyjys7n1fWSZPR7f+m89OiQ7EKC MFyQlgYIUmNSaBS4U+3hp9YypOOKETA8SxE3P2OSYXfPXVMnzl910pUO5rHaZiy4Ri hnXrtILvNHx/2oGjGOzX0m/F0sXHx1yKRkVdOsToWPyyO80oseHlPfP4EHJ9AOY9EY ssWtGzl+OJMnlDCdx2zClV1e4hoInhM3QT+G70Q2f1zxZv2PqqkDLct+2kIPxLfSpJ kXxQDv83uZplg== From: Daniel Gustafsson Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\)) Subject: Re: BUG #18569: Memory leak in Postgres Enterprise server Date: Tue, 6 Aug 2024 13:15:12 +0200 References: <18569-ba603937af37b1b6@postgresql.org> To: absahu@informatica.com, pgsql-bugs@lists.postgresql.org In-Reply-To: <18569-ba603937af37b1b6@postgresql.org> Message-Id: <4B5860EC-DBDB-464A-B744-C5091BF71659@yesql.se> X-Mailer: Apple Mail (2.3774.600.62) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 6 Aug 2024, at 10:34, PG Bug reporting form = wrote: > PostgreSQL Server/Client Version: PostgreSQL 16.2 Your report mentions "Postgres Enterprise Server", are you running a = product from a vendor like EDB or are you running postgres installed by yourself = via a package manager (or similar)? If you are buying postgres from a vendor = then please contact them, if not you are in the right place. Upgrading to the latest 16.3 is also recommended even though there are = no references to memory leak fixes in the release notes. > We have also attached our Repository logs, PostgreSQL server logs and = DB > logs. No, there are no logs attached (I don't think the bugreporting form = support attaching any files). Please provide additional information as there is nothing to go in the report. -- Daniel Gustafsson