Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 25428951979 for ; Thu, 10 Nov 2011 23:04:58 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 34714-10 for ; Fri, 11 Nov 2011 03:04:51 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0-rc2 Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by mail.postgresql.org (Postfix) with ESMTP id 3DB1C951978 for ; Thu, 10 Nov 2011 23:04:50 -0400 (AST) Received: by pzk33 with SMTP id 33so7151856pzk.3 for ; Thu, 10 Nov 2011 19:04:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language:x-antivirus:x-antivirus-status; bh=SvqzuJfFXvlG4F09RjpfzWvPUldErmW+MjvThoQN1q0=; b=IhleC6zhgA9a3NOT4+nvWSNnXj27D8KKpjxkHf5RWkkwXqGNYO9tmicaQaHwwcu7Q8 IoQNXba1lOU/yfRUWNQ+ZTbf2pZJE4sY7ky8fpvwlxC4yofmmujRClki9KcktC0npSNe O7Y9Wq9nGHqlOx3w5PfzG77FmNzovhyvmzKYc= Received: by 10.68.14.105 with SMTP id o9mr19698739pbc.95.1320980690273; Thu, 10 Nov 2011 19:04:50 -0800 (PST) Received: from shreeVAIO ([117.195.97.85]) by mx.google.com with ESMTPS id wn14sm26436684pbb.5.2011.11.10.19.04.46 (version=SSLv3 cipher=OTHER); Thu, 10 Nov 2011 19:04:48 -0800 (PST) From: "Shridhar Polas" To: Subject: Deadlock like scenario Date: Fri, 11 Nov 2011 08:34:47 +0530 Message-ID: <004b01cca01e$ae297f80$0a7c7e80$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_004C_01CCA04C.C7E67670" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AcygHRAfRm4zhn85Q1GRUwhaypHgiw== Content-Language: en-us X-Antivirus: avast! (VPS 111110-1, 11/11/2011), Outbound message X-Antivirus-Status: Clean X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.898 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 201111/52 X-Sequence-Number: 38646 This is a multipart message in MIME format. ------=_NextPart_000_004C_01CCA04C.C7E67670 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Hi, I am experience the problem where locks acquired by postgres are NOT getting released. The use case is something like:- . There is a table let's say "A" and the trigger is created on this table let say "A_TRIGGER". . The trigger captures the data change happens in table A into table B. . There would be a huge insert, update, delete on table A, the side effect of it table B also get updated very frequently. . There is periodic job that runs every midnight to do full vacuum and re-indexing on table B (but NOT on table A). . It has been found that the queries are hanging and never completes when there are some operation on table A. Can someone please help me out to resolve this problem. If someone need more information on this then please let me know. Thanks in advance, Shridhar ------=_NextPart_000_004C_01CCA04C.C7E67670 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Hi,

I am = experience the problem where locks acquired by postgres are NOT getting = released.

The use case is something like:-

· = There is a table let’s say = “A” and the trigger is created on this table let say = “A_TRIGGER”.

· = The trigger captures the data change = happens in table A into table B.

· = There would be a huge insert, update, = delete on table A, the side effect of it table B also get updated very = frequently.

· = There is periodic job that runs every = midnight to do full vacuum and re-indexing on table B (but NOT on table = A).

· = It has been found that the queries are = hanging and never completes when there are some operation on table = A.

Can someone = please help me out to resolve this problem. If someone need more = information on this then please let me know.

Thanks in = advance,

Shridhar

------=_NextPart_000_004C_01CCA04C.C7E67670--