X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id D8D7B9DC810 for ; Wed, 14 Dec 2005 05:21:53 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 07087-07 for ; Wed, 14 Dec 2005 05:21:52 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from svana.org (svana.org [203.20.62.76]) by postgresql.org (Postfix) with ESMTP id 32A6A9DC81E for ; Wed, 14 Dec 2005 05:21:49 -0400 (AST) Received: from kleptog by svana.org with local (Exim 3.35 #1 (Debian)) id 1EmSpR-0004WP-00; Wed, 14 Dec 2005 20:21:41 +1100 Date: Wed, 14 Dec 2005 10:21:41 +0100 From: Martijn van Oosterhout To: John Sidney-Woollett Cc: Tom Lane , pgsql general Subject: Re: Memory Leakage Problem Message-ID: <20051214092137.GA16967@svana.org> Reply-To: Martijn van Oosterhout Mail-Followup-To: John Sidney-Woollett , Tom Lane , pgsql general References: <6353.1134016733@sss.pgh.pa.us> <439DDB49.3000905@freedomhealthcare.org> <439E7B7A.9080205@wardbrook.com> <3666.1134460063@sss.pgh.pa.us> <439E80B1.8030800@wardbrook.com> <6375.1134486792@sss.pgh.pa.us> <6597.195.152.219.3.1134491862.squirrel@mercury.wardbrook.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AhhlLboLdkugWU4S" Content-Disposition: inline In-Reply-To: <6597.195.152.219.3.1134491862.squirrel@mercury.wardbrook.com> User-Agent: Mutt/1.3.28i X-PGP-Key-ID: Length=1024; ID=0x0DC67BE6 X-PGP-Key-Fingerprint: 295F A899 A81A 156D B522 48A7 6394 F08A 0DC6 7BE6 X-PGP-Key-URL: X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.047 required=5 tests=[AWL=0.047] X-Spam-Score: 0.047 X-Spam-Level: X-Archive-Number: 200512/688 X-Sequence-Number: 88251 --AhhlLboLdkugWU4S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 13, 2005 at 04:37:42PM -0000, John Sidney-Woollett wrote: > I'll run this over the next few days and especially as the server starts > bogging down to see if it identifies the culprit. >=20 > Is it possible to grab memory outsize of a processes space? Or would a > leak always show up by an ever increasing VSZ amount? The only way to know what a process can access is by looking in /proc//maps. This lists all the memory ranges a process can access. The thing about postgres is that each backend dies when the connection closes, so only a handful of processes are going to be around long enough to cause a problem. The ones you need to look at are the number of mappings with a zero-inode excluding the shared memory segment. A diff between two days might tell you which segments are growing. Must be for exactly the same process to be meaningful. Have a nice day, --=20 Martijn van Oosterhout http://svana.org/kleptog/ > Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a > tool for doing 5% of the work and then sitting around waiting for someone > else to do the other 95% so you can sue them. --AhhlLboLdkugWU4S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQFDn+QhIB7bNG8LQkwRAkjkAJ44/Ma4ZorBghQhnd5c9BZL2AxiYwCbBdWs T/rAoXwOlskZeM1XskRgouM= =XKzb -----END PGP SIGNATURE----- --AhhlLboLdkugWU4S--