From ciolofan@ics.forth.gr Fri May 11 13:57:37 2007 Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 8D7CB9FC272; Fri, 11 May 2007 10:57:37 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 40813-05; Fri, 11 May 2007 10:57:26 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mailhost.ics.forth.gr (mailhost.ics.forth.gr [139.91.157.55]) by postgresql.org (Postfix) with ESMTP id A31129FC26D; Fri, 11 May 2007 10:57:32 -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 l4BDvUQt002097; Fri, 11 May 2007 16:57:30 +0300 Received: from sappho.ics.forth.gr (unknown [127.0.0.1]) by mailhost.ics.forth.gr (Symantec Mail Security) with ESMTP id 0700B16C061; Fri, 11 May 2007 16:57:30 +0300 (EEST) X-AuditID: 7f000001-a2f23bb000003e42-9e-46447648e1de Received: from SHADOWFAX (unknown [139.91.183.33]) by mailhost.ics.forth.gr (Symantec Mail Security) with ESMTP id ECEDB8E40FC; Fri, 11 May 2007 16:57:27 +0300 (EEST) From: "Sorin N. Ciolofan" To: , Subject: increasing of the shared memory does not solve the problem of "OUT of shared memory" Date: Fri, 11 May 2007 16:58:28 +0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0040_01C793ED.990BAD40" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 thread-index: AceT1HORybHIbS0oRzqzVB7p3rbooA== Message-Id: <20070511135727.ECEDB8E40FC@mailhost.ics.forth.gr> X-Brightmail-Tracker: AAAAAA== X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/95 X-Sequence-Number: 25415 This is a multi-part message in MIME format. ------=_NextPart_000_0040_01C793ED.990BAD40 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello! 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? With best regards, Sorin N. Ciolofan ------=_NextPart_000_0040_01C793ED.990BAD40 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

Hello!

 

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?

 

With best regards,

Sorin N. Ciolofan

 

 

------=_NextPart_000_0040_01C793ED.990BAD40-- From adamtaunowilliams@gmail.com Fri May 11 18:42:48 2007 Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 5B5CE9FB760 for ; Fri, 11 May 2007 15:42:48 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 27683-09 for ; Fri, 11 May 2007 15:42:36 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.178]) by postgresql.org (Postfix) with ESMTP id 57AD89FB3EA for ; Fri, 11 May 2007 15:42:43 -0300 (ADT) Received: by py-out-1112.google.com with SMTP id a73so891428pye for ; Fri, 11 May 2007 11:42:42 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:subject:from:reply-to:to:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=HpZ9sCLBehC/orjQXcxATNJhETwlXzw+v+ampcgxm6hTNQSuOnJjOTTH8mm9mT0JU4Q/5Yee3PoZja8knVlSmjm4LZ2fYjqZ9xUfnsOmA5EdRfZ56cEDhBlOjbzLFpHtzqx6iPL8uDhgmoqhxUdFjSmqPNj6+X4RVfOLeQPIIQE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:subject:from:reply-to:to:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=JI4YIAwmmWI71pmEJakQr1FnLxIVrgheqiju5ARb0h2XnJ/5rroSl8h8fk0GQcBx+2o57zcsSpEvUOmXTEzvei35SkRs5hc0t0UmH3Qak/qc9UnJJDmsQEkATZ+IhVxblRQ3LlofFzppwiV52JIJ322PGdjHCEkfNvYhZgvKVB0= Received: by 10.35.106.1 with SMTP id i1mr5490548pym.1178908962393; Fri, 11 May 2007 11:42:42 -0700 (PDT) Received: from ?192.168.1.83? ( [206.114.45.106]) by mx.google.com with ESMTP id 12sm48357679nzn.2007.05.11.11.42.41; Fri, 11 May 2007 11:42:41 -0700 (PDT) Subject: Re: increasing of the shared memory does not solve the problem of "OUT of shared memory" From: Adam Tauno Williams Reply-To: adamtaunowilliams@gmail.com To: pgsql-admin@postgresql.org In-Reply-To: <20070511135727.ECEDB8E40FC@mailhost.ics.forth.gr> References: <20070511135727.ECEDB8E40FC@mailhost.ics.forth.gr> Content-Type: text/plain Date: Fri, 11 May 2007 14:41:37 -0400 Message-Id: <1178908897.4331.63.camel@aleph.whitemice.org> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/96 X-Sequence-Number: 25416 > 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 From tgl@sss.pgh.pa.us Fri May 11 23:31:07 2007 Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 3F5119FC31C; Fri, 11 May 2007 20:31:07 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 39874-02-7; Fri, 11 May 2007 20:30:44 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 7332B9FC397; Fri, 11 May 2007 20:12:32 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr4.postgresql.org (Postfix) with ESMTP id B6CC05AF8F3; Fri, 11 May 2007 20:43:59 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l4BKQAki002874; Fri, 11 May 2007 16:26:10 -0400 (EDT) To: "Sorin N. Ciolofan" Cc: pgsql-admin@postgresql.org, pgsql-general@postgresql.org Subject: Re: increasing of the shared memory does not solve the problem of "OUT of shared memory" In-reply-to: <20070511135727.ECEDB8E40FC@mailhost.ics.forth.gr> References: <20070511135727.ECEDB8E40FC@mailhost.ics.forth.gr> Comments: In-reply-to "Sorin N. Ciolofan" message dated "Fri, 11 May 2007 16:58:28 +0300" Date: Fri, 11 May 2007 16:26:10 -0400 Message-ID: <2873.1178915170@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/97 X-Sequence-Number: 25417 "Sorin N. Ciolofan" 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 From decibel@decibel.org Sat May 12 22:16:32 2007 Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 3E64F9FB7EC; Sat, 12 May 2007 19:16:32 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 73734-04; Sat, 12 May 2007 19:16:28 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id CD61D9FB7CC; Sat, 12 May 2007 19:16:28 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 9798F564AD; Sat, 12 May 2007 17:16:27 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Sat, 12 May 2007 17:16:25 -0500 Date: Sat, 12 May 2007 17:16:25 -0500 From: "Jim C. Nasby" To: "Sorin N. Ciolofan" Cc: pgsql-admin@postgresql.org, pgsql-general@postgresql.org Subject: Re: increasing of the shared memory does not solve the problem of "OUT of shared memory" Message-ID: <20070512221624.GD58786@nasby.net> References: <20070511135727.ECEDB8E40FC@mailhost.ics.forth.gr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070511135727.ECEDB8E40FC@mailhost.ics.forth.gr> X-Operating-System: FreeBSD 6.1-RELEASE-p10 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.13 (2006-08-11) X-Hashcash: 1:20:070512:ciolofan@ics.forth.gr::mCfjRnvbdns4VdJ2:0000000000000000 0000000000000000000000003iah X-Hashcash: 1:20:070512:pgsql-admin@postgresql.org::kZ+xJ4+H6vcAp7gh:00000000000 0000000000000000000000001Y3e X-Hashcash: 1:20:070512:pgsql-general@postgresql.org::2ODx3VZy4baM4kZg:000000000 0000000000000000000000000Ujp X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/102 X-Sequence-Number: 25422 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) From ciolofan@ics.forth.gr Thu May 17 09:13:36 2007 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-- From decibel@decibel.org Tue May 29 07:58:03 2007 Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id A6B2D9FB80F; Tue, 29 May 2007 04:58:03 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 78705-04; Tue, 29 May 2007 04:57:48 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id CE9F49FB280; Tue, 29 May 2007 04:57:56 -0300 (ADT) Received: from [192.168.50.99] (unknown [12.46.199.235]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by noel.decibel.org (Postfix) with ESMTP id 43C9A56492; Tue, 29 May 2007 02:57:50 -0500 (CDT) In-Reply-To: <20070517091322.3124E8E40FC@mailhost.ics.forth.gr> References: <20070517091322.3124E8E40FC@mailhost.ics.forth.gr> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: , , Content-Transfer-Encoding: 7bit From: Jim Nasby Subject: Re: increasing of the shared memory does not solve theproblem of "OUT of shared memory" Date: Mon, 28 May 2007 20:10:23 -0500 To: Sorin N. Ciolofan X-Mailer: Apple Mail (2.752.3) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/299 X-Sequence-Number: 25619 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)