From: Tom Lane <tgl@sss.pgh.pa.us>
To: Sebastian Gabbert <pg@huehnerhose.de>
cc: pgsql-admin@lists.postgresql.org
Subject: Re: backend proccess memory accumulates
In-reply-to: <6E65FD77-6FA1-485E-AEF2-318B56964255@huehnerhose.de>
References: <6E65FD77-6FA1-485E-AEF2-318B56964255@huehnerhose.de>
Comments: In-reply-to Sebastian Gabbert <pg@huehnerhose.de>
	message dated "Thu, 22 Nov 2018 16:15:28 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <5454.1542903991.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 22 Nov 2018 11:26:31 -0500
Message-ID: <5455.1542903991@sss.pgh.pa.us>
Precedence: bulk

Sebastian Gabbert <pg@huehnerhose.de> writes:
> Postgres is running on a dedicated FreeBSD 11.2 server with 32GB of RAM,=
 there is a second server in hot standby / wal replication. My =E2=80=9Cwo=
rker=E2=80=9D processes, mainly php processes, connect through pgbouncer (=
session mode).

> What I observed is that there are, at any time, around 10-15 postgres ba=
ckend processes on my main db server consuming around 4GB of memory (RES i=
n glances) each. These processes keep this footprint until pgbouncer close=
s the connection. =


That is, most likely, almost entirely shared space (shared buffers and so
on).  Sorting out how much is shared and how much is actually per-process
memory can be tricky, because most Unix process monitoring tools aren't
very good about showing the difference.  I don't use FreeBSD enough to be
sure how to tell the difference with its tools --- but you can't get
anywhere with diagnosing PG's true memory consumption until you've got a
handle on that.

It would be interesting to know what you've got shared_buffers set to
on this server, though.

			regards, tom lane