increasing of the shared memory does not solve the problem of "OUT of shared memory"

I increased significantly the number of shared buffers from 3000 to
100 000 (80Mb)
Also I increased the max_locks_per_transaction from 64 to 10 000.
I still receive the same error form Postgres:
org.postgresql.util.PSQLException: ERROR: out of shared memory
Is this message appropriate to the real cause of the problem or the
reason of the failure is actually other than what is displayed in this
message?

Maybe you've got an application that is doing a BEGIN WORK, but never
doing a rollback or commit?
--
Adam Tauno Williams, Network & Systems Administrator
Consultant - http://www.whitemiceconsulting.com
Developer - http://www.opengroupware.org

"Sorin N. Ciolofan" <ciolofan@ics.forth.gr> writes:

Also I increased the max_locks_per_transaction from 64 to 10 000.

I still receive the same error form Postgres:
org.postgresql.util.PSQLException: ERROR: out of shared memory

Did you remember to restart the postmaster after doing that? (pg_ctl
reload isn't good enough, you need an actual restart to enlarge shared
memory.) You can confirm whether it's really taken effect with
"show max_locks_per_transaction".

regards, tom lane

On Fri, May 11, 2007 at 04:58:28PM +0300, Sorin N. Ciolofan wrote:

I increased significantly the number of shared buffers from 3000 to 100 000
(80Mb)

BTW, 100,000 shared buffers is actually 800MB, not 80.
--
Jim Nasby jim@nasby.net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

Hi again!

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?

With best regards,

Sorin C.

-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Adam Tauno Williams
Sent: Friday, May 11, 2007 9:42 PM
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] increasing of the shared memory does not solve
theproblem of "OUT of shared memory"

I increased significantly the number of shared buffers from 3000 to

100 000 (80Mb)

Also I increased the max_locks_per_transaction from 64 to 10 000.

I still receive the same error form Postgres:

org.postgresql.util.PSQLException: ERROR: out of shared memory

Is this message appropriate to the real cause of the problem or the

reason of the failure is actually other than what is displayed in this

message?

Maybe you've got an application that is doing a BEGIN WORK, but never

doing a rollback or commit?

--

Adam Tauno Williams, Network & Systems Administrator

Consultant - http://www.whitemiceconsulting.com

Developer - http://www.opengroupware.org

---------------------------(end of broadcast)---------------------------

TIP 9: In versions below 8.0, the planner will ignore your desire to

choose an index scan if your joining column's datatypes do not

match

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@nasby.net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)