Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Out of Memory - 8.2.4
- From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
- To: Marko Kreen <markokr(at)gmail(dot)com>
- Cc: Jeff Amiel <becauseimjeff(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org
- Subject: Re: Out of Memory - 8.2.4
- Date: Tue, 28 Aug 2007 18:26:41 -0400
Marko Kreen escribió: > I've experienced something similar. The reason turned out to be > combination of overcommit=off, big maint_mem and several parallel > vacuums for fast-changing tables. Seems like VACUUM allocates > full maint_mem before start, whatever the actual size of the table. Hmm. Maybe we should have VACUUM estimate how much is the maximum amount of memory that would be used, given the size of the table, and allocate only that much. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
- Follow-Ups:
- Re: Out of Memory - 8.2.4
- From: Tom Lane
- Re: Out of Memory - 8.2.4
- References:
- Out of Memory - 8.2.4
- From: Jeff Amiel
- Re: Out of Memory - 8.2.4
- From: Marko Kreen
- Out of Memory - 8.2.4
- Prev by Date: Re: Is there a better way to do this?
- Next by Date: Re: Question regarding autovacuum
- Previous by thread: Re: Out of Memory - 8.2.4
- Next by thread: Re: Out of Memory - 8.2.4
- Indexes: