Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 190F0B5DBEE for ; Fri, 17 Jun 2011 10:58:35 -0300 (ADT) 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 54618-08; Fri, 17 Jun 2011 13:58:19 +0000 (UTC) Received: from mx2.hub.org (mx2.hub.org [200.46.204.254]) by mail.postgresql.org (Postfix) with ESMTP id 7E2D4B5D944; Fri, 17 Jun 2011 10:58:19 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gw.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by mx2.hub.org (Postfix) with ESMTP id 8C75517582A9; Fri, 17 Jun 2011 10:58:18 -0300 (ADT) Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Fri, 17 Jun 2011 08:55:27 -0500 Message-Id: <4DFB167A020000250003E7C2@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.1 Date: Fri, 17 Jun 2011 08:55:22 -0500 From: "Kevin Grittner" To: ,, Subject: Re: Postgres 8.3.10 Alter Table Waiting issue References: <4DFB154B020000250003E7B8@gw.wicourts.gov> <4DFB167A020000250003E7C2@gw.wicourts.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FRT_PHARMAC=1, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201106/107 X-Sequence-Number: 37733 [please don't send a post to multiple lists] Pratheeban Jebasingh Tharmaraj wrote: > I am trying to add column to the table that's hanging. > > alter table hr_firms add column_name biginit; > > This is the lock I see in the db > > relation | 564709 | 586888 | | | | > | | | | 1/8 | 1871 | > AccessExclusiveLock | f So it's temporarily blocking, waiting for conflicting access to complete. > Is it known issue or any fix available? Don't modify the structure of the table at the same time as conflicting access against the table, or wait for the transactions performing the conflicting access to commit? You haven't described the other activity on the table or shown the other lock(s) involved in the blocking. Without more information, it's hard to be more specific. http://wiki.postgresql.org/wiki/Guide_to_reporting_problems -Kevin