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

Re: Vacuum running out of memory

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jonathan Foy <thefoy(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Vacuum running out of memory
Date: 2009-12-08 16:42:43
Message-ID: 13154.1260290563@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
Jonathan Foy <thefoy(at)gmail(dot)com> writes:
> I was wondering if that was the problem.  So I'm correct in thinking that
> the failure occurred when the vacuum tried to pull its 256 MB as defined in
> the maintenance_work_mem value, and the system just did not have enough
> available...any idea why that would suddenly start happening?  The indexes I
> created shouldn't have affected that, should they?

Not directly, AFAICS, but they could stretch out the time required to
vacuum their tables, thus possibly leading to vacuums overlapping that
didn't overlap before.  Just a guess though.  Another likely bet is
that this is just an effect of the overall system load increasing
over time (more backends == more memory needed).

			regards, tom lane

In response to

pgsql-performance by date

Next:From: Kevin GrittnerDate: 2009-12-08 16:48:02
Subject: Re: Optimizing Bitmap Heap Scan.
Previous:From: Greg StarkDate: 2009-12-08 16:41:13
Subject: Re: Vacuum running out of memory

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