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-25 17:31:59
Message-ID: 4CC578BF0200002500036DC0@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-admin
Nick <t32(at)2thebatcave(dot)com> wrote:
> Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> 
>> I've not seen anything remotely like that.  I wonder what's
>> different....
> 
> I did a test with the same postgres build (and autovacuum_naptime
> = 1 as well) on the same OS with only the system databases
> (postgres, template0, template1), and after the weekend the memory
> utilization was acceptable:
 
That's probably it.  Our shop normally has just one application
database in a cluster, and I can't think of any clusters with more
than three or four.  It sounds like there might be some sort of
memory leak when a vacuum worker switches databases.
 
-Kevin

In response to

pgsql-admin by date

Next:From: Matt CheslerDate: 2010-10-25 19:11:48
Subject: Problem with Streaming Replication/Hot Standby
Previous:From: NickDate: 2010-10-25 17:01:28
Subject: Re: autovacuum launcher process eating up 17G+ of ram?

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