Re: BUG #6716: memory of Autovacuum leak?

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: runner(dot)mei <runner(dot)mei(at)gmail(dot)com>
Cc: Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #6716: memory of Autovacuum leak?
Date: 2012-07-06 13:19:50
Message-ID: 1341580749-sup-8639@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


Excerpts from runner.mei's message of mié jul 04 10:03:42 -0400 2012:
> The following bug has been logged on the website:
>
> Bug reference: 6716
> Logged by: runner.mei
> Email address: runner(dot)mei(at)gmail(dot)com
> PostgreSQL version: 9.1.3
> Operating system: win2003
> Description:
>
> My program using a postgresql9.1.3, and running in win2003. Generally have
> 17-18 processes of postgresql, the memory of any process no more than 60M,
> but today the memory of a process to reach 880M.At first I thought it was
> temporary, but until now has been going on for 9 hours, and continues to
> grow.The parameters of the process for "- forkavlauncher -x3" someone can
> help me?

What's your maintenance_work_mem setting? Also, what does
pg_stat_activity say about that process?

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2012-07-06 17:31:53 Re: Problem with pg_upgrade
Previous Message Dave Page 2012-07-06 10:28:56 Re: BUG #6721: installation of PostgreSQL prevented WebServer Start