Re: ***UNCHECKED*** Re: memory leak occur when disconnect database - Mailing list pgsql-general

From Tom Lane
Subject Re: ***UNCHECKED*** Re: memory leak occur when disconnect database
Date
Msg-id 13164.1248188562@sss.pgh.pa.us
Whole thread Raw
In response to Re: ***UNCHECKED*** Re: memory leak occur when disconnect database  (Craig Ringer <craig@postnewspapers.com.au>)
List pgsql-general
Craig Ringer <craig@postnewspapers.com.au> writes:
> On Tue, 2009-07-21 at 10:13 -0400, Tom Lane wrote:
>> It's not unusual for "top" to show the postmaster's child processes as
>> "postmaster" as well.  Depends on the platform and the options given
>> to top.

> Ah. Thanks for clearing that one up. That'd make more sense, since it'd
> mean the postmaster, bgwriter, and whichever of the stats collector/wal
> writer exist in 8.1 were running.

Hmm ... actually an idle 8.1 cluster should have four processes.  Mine
looks like this:

     UID   PID  PPID  C    STIME TTY       TIME COMMAND
postgres  1643     1  0  Jul 17  ?         0:00 postmaster
postgres  1646  1643  0  Jul 17  ?         0:43 postgres: writer process
postgres  1647  1643  0  Jul 17  ?         0:00 postgres: stats buffer process
postgres  1648  1647  0  Jul 17  ?         0:00 postgres: stats collector process

If the OP had turned off stats collection then there would be only two,
so it still doesn't add up.  Maybe stats collection off and one live
backend?  Or maybe he missed the stats collector process --- notice in
the above that that's not a direct child of the postmaster, but a
grandchild.  Possibly top would show it with a different name.

            regards, tom lane

pgsql-general by date:

Previous
From: Sam Mason
Date:
Subject: Re: element from an array by its index
Next
From: Dennis Gearon
Date:
Subject: Re: commercial adaptation of postgres