Skip site navigation (1) Skip section navigation (2)

Re: autovacuum launcher process eating up 17G+ of ram?

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Nick" <t32(at)2thebatcave(dot)com>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: autovacuum launcher process eating up 17G+ of ram?
Date: 2010-10-22 18:17:42
Message-ID: 4CC18EF60200002500036CF3@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-admin
Nick <t32(at)2thebatcave(dot)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

In response to

Responses

pgsql-admin by date

Next:From: Guillaume LelargeDate: 2010-10-23 10:08:10
Subject: Re: Can't remove filter when no rows returned
Previous:From: NickDate: 2010-10-22 17:28:03
Subject: Re: autovacuum launcher process eating up 17G+ of ram?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group