From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Nick <t32@2thebatcave.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: autovacuum launcher process eating up 17G+ of ram?
Date: Fri, 22 Oct 2010 13:17:42 -0500
Message-ID: <4CC18EF60200002500036CF3@gw.wicourts.gov> (raw)
In-Reply-To: <AANLkTimKs23hytr6oj1Kco53rbaPF2mKTZZYofr0Cr0+@mail.gmail.com>
References: <AANLkTimGvWugpjwN1Ki=qmd56nsc4gXH6yKT5765nFPK@mail.gmail.com>
<4CC071670200002500036C8A@gw.wicourts.gov>
<AANLkTimKs23hytr6oj1Kco53rbaPF2mKTZZYofr0Cr0+@mail.gmail.com>
Nick <t32@2thebatcave.com> wrote:
> Here is a vmstat 1 right after postgres has been started:
>
> procs -----------memory----------
> r b swpd free buff cache
> 0 0 55480 760172 1709424 3758492
> Here is another chunk after it's been running for about 18 hours:
>
> procs -----------memory----------
> r b swpd free buff cache
> 0 0 1812168 20332 59452 102172
> Here is a snapshot of all the postgres processes as listed in top
> (29582 = postgres: autovacuum launcher process):
>
> 29582 pgsql 15 0 8739m 6.7g 1816 S 8.9 86.1 91:10.44
> postgres
Ouch!
I've not seen anything remotely like that. I wonder what's
different....
> As you can see, after a while the system is using a lot of swap.
> The first time I noticed the problem, the swap was up to 12G
> (there is 8GB of ram in this system). I believe postgres was
> running for several days to achieve that much memory utilization.
Is there anything unusual in the logs?
-Kevin
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-admin@postgresql.org
Cc: Kevin.Grittner@wicourts.gov, t32@2thebatcave.com
Subject: Re: autovacuum launcher process eating up 17G+ of ram?
In-Reply-To: <4CC18EF60200002500036CF3@gw.wicourts.gov>
* 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