From: | Jim Nasby <decibel(at)decibel(dot)org> |
---|---|
To: | Sorin N(dot) Ciolofan <ciolofan(at)ics(dot)forth(dot)gr> |
Cc: | <adamtaunowilliams(at)gmail(dot)com>, <pgsql-admin(at)postgresql(dot)org>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: increasing of the shared memory does not solve theproblem of "OUT of shared memory" |
Date: | 2007-05-29 01:10:23 |
Message-ID: | CCF63866-FDF0-4424-8452-FC9D2E1A8D80@decibel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
On May 17, 2007, at 4:14 AM, Sorin N. Ciolofan wrote:
> It seems that the problem was the max_fsm_relations parameter which
> was increased
> I still do not understand why in the past I received always the
> message:
>
> ERROR: out of shared memory
>
> Is this an appropriate message for the need for increasing this
> parameter?
Yes, increasing max_fsm_relations requires more shared memory. Theres
more information about this in the docs... search for shmmax.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2007-05-29 01:13:53 | Re: PostgreSQL Training? |
Previous Message | Michael Fuhr | 2007-05-28 21:40:08 | Re: Return record on recursive call |
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Browne | 2007-05-29 01:34:41 | Re: Stored Procedures Performance: Java vs. PL/Pgsql |
Previous Message | Jeff Davis | 2007-05-29 00:05:09 | Re: Uhm, so, yeah, speaking of /. |