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
