Lists: | pgsql-hackers |
---|
From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | SHMEM_INDEX_SIZE exceeded on startup |
Date: | 2011-03-29 17:20:00 |
Message-ID: | 4D91CE70020000250003BECF@gw.wicourts.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
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.
-Kevin
Attachment | Content-Type | Size |
---|---|---|
shmem-index-size.patch | text/plain | 685 bytes |
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 |
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