pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Martijn van Oosterhout <kleptog@svana.org>
To: John Sidney-Woollett <johnsw@wardbrook.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql general <pgsql-general@postgresql.org>
Subject: Re: Memory Leakage Problem
Date: Wed, 14 Dec 2005 10:21:41 +0100
Message-ID: <20051214092137.GA16967@svana.org> (raw)
In-Reply-To: <6597.195.152.219.3.1134491862.squirrel@mercury.wardbrook.com>
References: <c10e7feb0512071825h30c93c00kdf5ea2a11e613f0b@mail.gmail.com>
	<b918cf3d0512071946m3cbfc630y679e0350a7f6b864@mail.gmail.com>
	<6353.1134016733@sss.pgh.pa.us>
	<b918cf3d0512080600q5c841fc8lecd96c3bad66cfdc@mail.gmail.com>
	<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>

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.
> 
> 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/<pid>/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,
-- 
Martijn van Oosterhout   <kleptog@svana.org>   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.

view thread (22+ messages)  latest in thread

Message-ID: <20051214092137.GA16967@svana.org>
Permalink:  ../20051214092137.GA16967@svana.org/
Also on:    postgresql.org/message-id/20051214092137.GA16967@svana.org

 · 

reply
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-performance@postgresql.org
  Cc: kleptog@svana.org, johnsw@wardbrook.com, tgl@sss.pgh.pa.us, pgsql-general@postgresql.org
  Subject: Re: Memory Leakage Problem
  In-Reply-To: <20051214092137.GA16967@svana.org>

* 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