Re: [COMMITTERS] pgsql: Reduce the size ofmemoryallocations by lazy vacuum when

From: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: "Alvaro Herrera" <alvherre(at)postgresql(dot)org>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Reduce the size ofmemoryallocations by lazy vacuum when
Date: 2007-09-24 10:34:23
Message-ID: 46F792AF.8010705@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Simon Riggs wrote:
> On Mon, 2007-09-24 at 10:39 +0100, Heikki Linnakangas wrote:
>> Let's keep it simple. Per-table setting would be much more complex and
>> would be something that the DBA would need to calculate and set. If you
>> really do run into this problem, you can just dial down
>> maintenance_work_mem.
>
> Much more complex? RelationGetAvgFSM(relation)??

The code isn't complex, but the resulting behavior is.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Gregory Stark 2007-09-24 11:48:01 Re: [COMMITTERS] pgsql: Reduce the size of memoryallocations by lazy vacuum when
Previous Message Simon Riggs 2007-09-24 10:23:01 Re: [COMMITTERS] pgsql: Reduce the size of memoryallocations by lazy vacuum when

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2007-09-24 10:45:13 Re: CREATE DATABASE cannot be executed from a function or multi-command string
Previous Message Heikki Linnakangas 2007-09-24 10:30:41 Re: CREATE DATABASE cannot be executed from a function or multi-command string