Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 243389FBD68; Fri, 30 Mar 2007 10:19:39 -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 98896-07; Fri, 30 Mar 2007 10:19:24 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 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 B595B9FBC6D; Fri, 30 Mar 2007 10:19:29 -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 l2UDJRcj011284; Fri, 30 Mar 2007 16:19:27 +0300 X-DKIM: Sendmail DKIM Filter v0.6.1 mailhost.ics.forth.gr l2UDJRcj011284 DKIM-Signature: v=0.5; a=rsa-sha256; c=simple/simple; d=ics.forth.gr; s=mailhost; t=1175260767; bh=bi2DNtH96PB3UVQZvv3DbRVa+QiyXZEd8p/r1L fceXc=; h=Received:X-AuditID:Received:From:To:Cc:Subject:Date: MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer: Thread-Index:In-Reply-To:X-MimeOLE:Message-Id: X-Brightmail-Tracker; b=vQ0JHJWyqMq3pKvGhrPJhOMEUGFeQ1WFzBJSR1ViR5 /xMFQycAhgF+/aEb/pM3ofNBO95JilJBysfOYDw8MhFRseavwrYxz7WpaM0BuBZ2Tjd Tf+VmTRv39EiJP7d6ZJE9EQ+/gSe4AGGMkj9wuJL16TkkSLGH73RmpUGxVMLQI= Received: from sappho.ics.forth.gr (unknown [127.0.0.1]) by mailhost.ics.forth.gr (Symantec Mail Security) with ESMTP id 3562216C061; Fri, 30 Mar 2007 16:19:27 +0300 (EEST) X-AuditID: 7f000001-ac8e3bb00000050a-6c-460d0e5e7eca Received: from SHADOWFAX (unknown [139.91.183.33]) by mailhost.ics.forth.gr (Symantec Mail Security) with ESMTP id B9DC18E40FC; Fri, 30 Mar 2007 16:19:26 +0300 (EEST) From: "Sorin N. Ciolofan" To: "'Tom Lane'" Cc: , , Subject: Re: ERROR: out of shared memory Date: Fri, 30 Mar 2007 16:20:09 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcdweCyZG6Ld6NOySHy9xj/0pDMfbQCVVR0A In-Reply-To: <19352.1175003955@sss.pgh.pa.us> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Message-Id: <20070330131926.B9DC18E40FC@mailhost.ics.forth.gr> X-Brightmail-Tracker: AAAAAA== X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.051 tagged_above=0 required=5 tests=AWL=0.052, BAYES_50=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 X-Spam-Level: X-Archive-Number: 200704/39 X-Sequence-Number: 111942 Dear Mr. Tom Lane, From what I've read from the postgresql.conf file I've understood that which each unit increasing of the "max_locks_per_transaction" parameter the shared memory used is also increased. But the shared memory looks to be already fully consumed according to the error message, or is the error message irrelevant and improper in this situation? With best regards, Sorin -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Tuesday, March 27, 2007 4:59 PM To: Sorin N. Ciolofan Cc: pgsql-general@postgresql.org; pgsql-admin@postgresql.org; pgsql-performance@postgresql.org Subject: Re: [GENERAL] ERROR: out of shared memory "Sorin N. Ciolofan" writes: > It seems that the legacy application creates tables dynamically and the > number of the created tables depends on the size of the input of the > application. For the specific input which generated that error I've > estimated a number of created tables of about 4000. > Could be this the problem? If you have transactions that touch many of them within one transaction, then yup, you could be out of locktable space. Try increasing max_locks_per_transaction. regards, tom lane