Re: SHMEM_INDEX_SIZE exceeded on startup

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: SHMEM_INDEX_SIZE exceeded on startup
Date: 2011-03-31 10:41:46
Message-ID: 4D945A6A.1050104@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 29.03.2011 20:20, Kevin Grittner wrote:
> I doubt that this is going to matter much, and should only have a
> trivial impact on shared space calculations and postmaster and
> connection startup time, but just as a matter of principle we might
> want to set SHMEM_INDEX_SIZE at least as large as the number of
> entries in ShmemIndex. At startup that seems to be 40 as of current
> HEAD.
>
> Trivial patch attached.

Ok, committed.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bernd Helmle 2011-03-31 12:35:43 Re: BUG #5856: pg_attribute.attinhcount is not correct.
Previous Message Heikki Linnakangas 2011-03-31 10:31:24 Re: crash-safe visibility map, take four