Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 60F7C9FB40A; Thu, 17 May 2007 06:13:36 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 42750-02; Thu, 17 May 2007 06:13:30 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mailhost.ics.forth.gr (mailhost.ics.forth.gr [139.91.157.55]) by postgresql.org (Postfix) with ESMTP id 427F89FB400; Thu, 17 May 2007 06:13:30 -0300 (ADT) Received: from mailhost.ics.forth.gr (mailhost.ics.forth.gr [139.91.157.55] (may be forged)) by mailhost.ics.forth.gr (8.13.8/ICS-FORTH/V10-Server-2.0.0) with ESMTP id l4H9DMnw020908; Thu, 17 May 2007 12:13:23 +0300 Received: from sappho.ics.forth.gr (unknown [127.0.0.1]) by mailhost.ics.forth.gr (Symantec Mail Security) with ESMTP id CC85316C061; Thu, 17 May 2007 12:13:22 +0300 (EEST) X-AuditID: 7f000001-a7cc8bb000001a55-a2-464c1cb268ff Received: from SHADOWFAX (unknown [139.91.183.33]) by mailhost.ics.forth.gr (Symantec Mail Security) with ESMTP id 3124E8E40FC; Thu, 17 May 2007 12:13:22 +0300 (EEST) From: "Sorin N. Ciolofan" To: , Cc: Subject: Re: increasing of the shared memory does not solve theproblem of "OUT of shared memory" Date: Thu, 17 May 2007 12:14:17 +0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0074_01C7987C.E42057C0" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <1178908897.4331.63.camel@aleph.whitemice.org> Thread-Index: AceT/IejtVhkKnQRR2aA7aS4JL7dnQEZrhuw X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Message-Id: <20070517091322.3124E8E40FC@mailhost.ics.forth.gr> X-Brightmail-Tracker: AAAAAA== X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/154 X-Sequence-Number: 25474 This is a multi-part message in MIME format. ------=_NextPart_000_0074_01C7987C.E42057C0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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 ------=_NextPart_000_0074_01C7987C.E42057C0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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

------=_NextPart_000_0074_01C7987C.E42057C0--