From ciolofan@ics.forth.gr Mon Mar 26 14:07:48 2007 Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id B49D29FB39E; Mon, 26 Mar 2007 11:07:48 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 25816-06; Mon, 26 Mar 2007 11:07:37 -0300 (ADT) X-Greylist: delayed 01:36:12.039481 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 34BBE9FB368; Mon, 26 Mar 2007 11:07:42 -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 l2QCVSs8017338; Mon, 26 Mar 2007 15:31:28 +0300 Received: from sappho.ics.forth.gr (unknown [127.0.0.1]) by mailhost.ics.forth.gr (Symantec Mail Security) with ESMTP id 2AB7916C061; Mon, 26 Mar 2007 15:31:28 +0300 (EEST) X-AuditID: 7f000001-aad9fbb00000050a-3e-4607bd1f4e53 Received: from SHADOWFAX (unknown [139.91.183.33]) by mailhost.ics.forth.gr (Symantec Mail Security) with ESMTP id 55F808E40FC; Mon, 26 Mar 2007 15:31:27 +0300 (EEST) From: "Sorin N. Ciolofan" To: Cc: , Subject: ERROR: out of shared memory Date: Mon, 26 Mar 2007 15:32:08 +0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0045_01C76FBB.EA3640A0" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 thread-index: AcdvosTM0Er21xsKTJu5Z+iMXGS6Hg== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Message-Id: <20070326123127.55F808E40FC@mailhost.ics.forth.gr> X-Brightmail-Tracker: AAAAAA== X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.014 tagged_above=0 required=5 tests=BAYES_40, DNS_FROM_RFC_ABUSE, HTML_MESSAGE, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200703/217 X-Sequence-Number: 25041 This is a multi-part message in MIME format. ------=_NextPart_000_0045_01C76FBB.EA3640A0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello! I have to manage an application written in java which call another module written in java which uses Postgre DBMS in a Linux environment. I'm new to Postgres. The problem is that for large amounts of data the application throws an: org.postgresql.util.PSQLException: ERROR: out of shared memory Please, have you any idea why this error appears and what can I do in order to fix this? Are there some Postgre related parameters I should tune (if yes what parameters) or is something related to the Linux OS? Thank you very much With best regards, Sorin ------=_NextPart_000_0045_01C76FBB.EA3640A0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

    = Hello!

 

   I have to manage an application = written in java which call another module written in java which uses Postgre = DBMS in a Linux environment. I’m new to Postgres. The problem is that for = large amounts of data the application throws an:

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

 

Please, have you any idea why this error = appears and what can I do in order to fix this?

Are there some Postgre related parameters I = should tune (if yes what parameters) or is something related to the Linux = OS?

 

Thank you very = much

With best = regards,

Sorin

------=_NextPart_000_0045_01C76FBB.EA3640A0-- From tgl@sss.pgh.pa.us Tue Mar 27 03:38:58 2007 Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id B4B849FBC7F; Tue, 27 Mar 2007 00:38:58 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 65405-01-9; Tue, 27 Mar 2007 00:38:50 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id ABD819FB7B9; Tue, 27 Mar 2007 00:37:51 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l2R3bIxk011070; Mon, 26 Mar 2007 23:37:18 -0400 (EDT) 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 In-reply-to: <20070326123127.55F808E40FC@mailhost.ics.forth.gr> References: <20070326123127.55F808E40FC@mailhost.ics.forth.gr> Comments: In-reply-to "Sorin N. Ciolofan" message dated "Mon, 26 Mar 2007 15:32:08 +0300" Date: Mon, 26 Mar 2007 23:37:18 -0400 Message-ID: <11069.1174966638@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/202 X-Sequence-Number: 25026 "Sorin N. Ciolofan" writes: > I have to manage an application written in java which call another module > written in java which uses Postgre DBMS in a Linux environment. I'm new to > Postgres. The problem is that for large amounts of data the application > throws an: > org.postgresql.util.PSQLException: ERROR: out of shared memory AFAIK the only very likely way to cause that is to touch enough different tables in one transaction that you run out of lock entries. While you could postpone the problem by increasing the max_locks_per_transaction setting, I suspect there may be some basic application misdesign involved here. How many tables have you got? regards, tom lane From mmoncure@gmail.com Tue Mar 27 13:06:46 2007 Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id F12179FB58C for ; Tue, 27 Mar 2007 10:06:46 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 56607-07 for ; Tue, 27 Mar 2007 10:06:36 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by postgresql.org (Postfix) with ESMTP id D57D79FB560 for ; Tue, 27 Mar 2007 10:06:41 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id k3so1745535ugf for ; Tue, 27 Mar 2007 06:06:39 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=AMJTzaglFxAmQE8isup/1/dXwuf4ILpSi0TLTbpPk06vsOOA93UZhHQYqNzAlY4UJu/96i2X46y3PUS+MaQ02Tq09P0DOOGjZII/37zlwZZCO0Jt5812Eiyh1sMOxYElHxfi7ZDDk31OcqWvlv9bbNQhVsmVzrErG92D1MSCxfQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Ty1vqXapuxycvsR5jGGw1yt2TcvvLkOt3dNPE80nXGRqHd51P4N3XjOifzXEDOK2fX1r1CY+NaSCpRo/6evkIqxxmZYgIO4q10A636FE3HDm2lt80x6k+pn2A0O6DofRkgwow0TbOA478/mPWowM+LRAxCJrhSR19HxmLHiuuwQ= Received: by 10.78.171.20 with SMTP id t20mr3524986hue.1175000798955; Tue, 27 Mar 2007 06:06:38 -0700 (PDT) Received: by 10.78.35.18 with HTTP; Tue, 27 Mar 2007 06:06:38 -0700 (PDT) Message-ID: Date: Tue, 27 Mar 2007 09:06:38 -0400 From: "Merlin Moncure" To: "Tom Lane" Subject: Re: [GENERAL] ERROR: out of shared memory Cc: "Sorin N. Ciolofan" , pgsql-general@postgresql.org, pgsql-admin@postgresql.org, pgsql-performance@postgresql.org In-Reply-To: <11069.1174966638@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070326123127.55F808E40FC@mailhost.ics.forth.gr> <11069.1174966638@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/210 X-Sequence-Number: 25034 On 3/26/07, Tom Lane wrote: > "Sorin N. Ciolofan" writes: > > I have to manage an application written in java which call another module > > written in java which uses Postgre DBMS in a Linux environment. I'm new to > > Postgres. The problem is that for large amounts of data the application > > throws an: > > org.postgresql.util.PSQLException: ERROR: out of shared memory > > AFAIK the only very likely way to cause that is to touch enough > different tables in one transaction that you run out of lock entries. > While you could postpone the problem by increasing the > max_locks_per_transaction setting, I suspect there may be some basic > application misdesign involved here. How many tables have you got? or advisory locks...these are easy to spot. query pg_locks and look for entries of locktype 'advisory'. I've already seen some apps in the wild that use them, openads is one. merlin From ciolofan@ics.forth.gr Tue Mar 27 13:13:08 2007 Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id E51569FB747; Tue, 27 Mar 2007 10:13:08 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 93954-02; Tue, 27 Mar 2007 10:12:58 -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 D909D9FB560; Tue, 27 Mar 2007 10:13:03 -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 l2RDD1R3030128; Tue, 27 Mar 2007 16:13:01 +0300 X-DKIM: Sendmail DKIM Filter v0.6.1 mailhost.ics.forth.gr l2RDD1R3030128 DKIM-Signature: v=0.5; a=rsa-sha256; c=simple/simple; d=ics.forth.gr; s=mailhost; t=1175001181; bh=52pwbHDdiUZbWYBbFdnkdcMPqojzbhYZicrm8B u6Gi4=; h=Received:X-AuditID:Received:From:To:Cc:Subject:Date: MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer: thread-index:X-MimeOLE:In-Reply-To:Message-Id: X-Brightmail-Tracker; b=amuuxm6RuT0TQ1PL9p3VqpsYnr6QpsK0iqllZ/SrcB iH/dQ6ceDdGBNGOn3yUg2H2wK86j3IxY67cJ9gR1cR6ByY0YA/Q94E4vfIKeV5C5L6b azE0XC56wU5Rd5Rlr2G4QX6aD+vAolOKf89Fxhsr3RZCweayIDJtgf17Qpk46s= Received: from sappho.ics.forth.gr (unknown [127.0.0.1]) by mailhost.ics.forth.gr (Symantec Mail Security) with ESMTP id 52A0E16C092; Tue, 27 Mar 2007 16:13:01 +0300 (EEST) X-AuditID: 7f000001-a859bbb00000050a-4c-4609185da36c Received: from SHADOWFAX (unknown [139.91.183.33]) by mailhost.ics.forth.gr (Symantec Mail Security) with ESMTP id 065E38E40FC; Tue, 27 Mar 2007 16:13:01 +0300 (EEST) From: "Sorin N. Ciolofan" To: "'Tom Lane'" Cc: , , Subject: Re: [GENERAL] ERROR: out of shared memory Date: Tue, 27 Mar 2007 16:13:42 +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: AcdwIUsgxMJeBjGfS6KihRH9XjNwhQAUGMAg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 In-Reply-To: <11069.1174966638@sss.pgh.pa.us> Message-Id: <20070327131301.065E38E40FC@mailhost.ics.forth.gr> X-Brightmail-Tracker: AAAAAA== X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.069 tagged_above=0 required=5 tests=AWL, BAYES_50, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200703/216 X-Sequence-Number: 25040 Dear Mr. Tom Lane, Thank you very much for your answer. 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? With best regards, Sorin -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Tuesday, March 27, 2007 6:37 AM 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: > I have to manage an application written in java which call another module > written in java which uses Postgre DBMS in a Linux environment. I'm new to > Postgres. The problem is that for large amounts of data the application > throws an: > org.postgresql.util.PSQLException: ERROR: out of shared memory AFAIK the only very likely way to cause that is to touch enough different tables in one transaction that you run out of lock entries. While you could postpone the problem by increasing the max_locks_per_transaction setting, I suspect there may be some basic application misdesign involved here. How many tables have you got? regards, tom lane From tgl@sss.pgh.pa.us Tue Mar 27 13:59:54 2007 Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 77CB19FB798; Tue, 27 Mar 2007 10:59:54 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 94112-01-2; Tue, 27 Mar 2007 10:59:40 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id B292F9FB7B8; Tue, 27 Mar 2007 10:59:45 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l2RDxFNm019353; Tue, 27 Mar 2007 09:59:15 -0400 (EDT) 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 In-reply-to: <20070327131301.065E38E40FC@mailhost.ics.forth.gr> References: <20070327131301.065E38E40FC@mailhost.ics.forth.gr> Comments: In-reply-to "Sorin N. Ciolofan" message dated "Tue, 27 Mar 2007 16:13:42 +0300" Date: Tue, 27 Mar 2007 09:59:15 -0400 Message-ID: <19352.1175003955@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/211 X-Sequence-Number: 25035 "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 From ciolofan@ics.forth.gr Fri Mar 30 13:19:39 2007 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 From jks@selectacast.net Fri Apr 6 00:25:15 2007 Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id C8B869FB704 for ; Thu, 5 Apr 2007 21:25:15 -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 94312-02 for ; Thu, 5 Apr 2007 21:25:15 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from floppy.pyrenet.fr (floppy.pyrenet.fr [194.116.145.2]) by postgresql.org (Postfix) with ESMTP id 49B4E9FB6D2 for ; Thu, 5 Apr 2007 21:25:15 -0300 (ADT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id CACB83090A; Fri, 6 Apr 2007 02:25:12 +0200 (MET DST) From: Joseph S X-Newsgroups: pgsql.general Subject: Re: ERROR: out of shared memory Date: Thu, 05 Apr 2007 20:25:11 -0400 Organization: Hub.Org Networking Services Lines: 1 Message-ID: <46159367.5030508@selectacast.net> References: <19352.1175003955@sss.pgh.pa.us> <20070330131926.B9DC18E40FC@mailhost.ics.forth.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org To: "Sorin N. Ciolofan" User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.10) Gecko/20070302 Fedora/1.5.0.10-1.fc6 pango-text Thunderbird/1.5.0.10 Mnenhy/0.7.4.0 In-Reply-To: <20070330131926.B9DC18E40FC@mailhost.ics.forth.gr> To: pgsql-general@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/283 X-Sequence-Number: 112186 Try doing select * from pg_locks to see how many locks you have out.