Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 826189F9FB2 for ; Wed, 6 Dec 2006 20:19:36 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 95740-03 for ; Wed, 6 Dec 2006 20:19:28 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from web58411.mail.re3.yahoo.com (web58411.mail.re3.yahoo.com [68.142.236.179]) by postgresql.org (Postfix) with SMTP id 4B6729F9F0E for ; Wed, 6 Dec 2006 20:19:28 -0400 (AST) Received: (qmail 59698 invoked by uid 60001); 7 Dec 2006 00:19:26 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=Zj5B817azerG4Y4rJLjCMOC3PayFWQd0DsW3saTovXXqGmnC/2QnMF3kPDMfpLq5nwXm+VjCh5G8eYpeXvVv408phEudJ8cGLZgRrmD5/zw6/JuA073Xm8iLzusmkCHKN8v97V7c3/U0mMb4i+xjIvbe7LBzNu8BhxRpGf/WrJs=; X-YMail-OSG: zcOihcMVM1l1mUE.HKO7zAGAr2JV1Vmaxcors.ZsO4CSvf6LXmJ5zuzj95ApJNgnHAxQaZSNDTJ1up99A73JsqPnEBXfQKLcRe8Jqn9dGDcC_JEBPmRGuUdMTjgXZyfbFCpDo.ObPYkzaD8- Received: from [65.218.233.130] by web58411.mail.re3.yahoo.com via HTTP; Wed, 06 Dec 2006 16:19:26 PST Date: Wed, 6 Dec 2006 16:19:26 -0800 (PST) From: asif ali Subject: Re: VACUUM FULL does not works....... To: pgsql-performance@postgresql.org In-Reply-To: <1165443208.3243.17.camel@state.g2switchworks.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1348166326-1165450766=:59076" Content-Transfer-Encoding: 8bit Message-ID: <325721.59076.qm@web58411.mail.re3.yahoo.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.641 tagged_above=0 required=5 tests=AWL, BAYES_50, DNS_FROM_RFC_ABUSE, DNS_FROM_RFC_POST, DNS_FROM_RFC_WHOIS, HTML_MESSAGE X-Spam-Level: * X-Archive-Number: 200612/160 X-Sequence-Number: 22216 --0-1348166326-1165450766=:59076 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Thanks Scott, It worked!!! We killed an old idle running transaction, now everything is fine.. Thanks Again asif ali icrossing inc Scott Marlowe wrote: On Wed, 2006-12-06 at 15:53, asif ali wrote: > Thanks Everybody for helping me out. > I checked "pg_stat_activity"/pg_locks, but do not see any activity on > the table. > How to find a old running transaction... > I saw this link, but it did not help.. > http://archives.postgresql.org/pgsql-hackers/2005-02/msg00760.php Sometimes just using top or ps will show you. on linux you can run top and then hit c for show command line and look for ones that are IDLE Or, try ps: ps axw|grep postgres On my machine normally: 2408 ? S 0:00 /usr/local/pgsql/bin/postmaster -p 5432 -D /home/postgres/data 2615 ? S 0:00 postgres: stats buffer process 2616 ? S 0:00 postgres: stats collector process 2857 ? S 0:00 postgres: writer process 2858 ? S 0:00 postgres: stats buffer process 2859 ? S 0:00 postgres: stats collector process But with an idle transaction: 2408 ? S 0:00 /usr/local/pgsql/bin/postmaster -p 5432 -D /home/postgres/data 2615 ? S 0:00 postgres: stats buffer process 2616 ? S 0:00 postgres: stats collector process 2857 ? S 0:00 postgres: writer process 2858 ? S 0:00 postgres: stats buffer process 2859 ? S 0:00 postgres: stats collector process 8679 ? S 0:00 postgres: smarlowe test [local] idle in transaction Thar she blows! Also, you can restart the database and vacuum it then too. Of course, don't do that during regular business hours... ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings --------------------------------- Have a burning question? Go to Yahoo! Answers and get answers from real people who know. --0-1348166326-1165450766=:59076 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Thanks Scott,
It worked!!!
We killed an old idle running transaction, now everything is fine..

Thanks Again
asif ali
icrossing inc

Scott Marlowe <smarlowe@g2switchworks.com> wrote:
On Wed, 2006-12-06 at 15:53, asif ali wrote:
> Thanks Everybody for helping me out.
> I checked "pg_stat_activity"/pg_locks, but do not see any activity on
> the table.
> How to find a old running transaction...
> I saw this link, but it did not help..
> http://archives.postgresql.org/pgsql-hackers/2005-02/msg00760.php

Sometimes just using top or ps will show you.

on linux you can run top and then hit c for show command line and look
for ones that are IDLE

Or, try ps:

ps axw|grep postgres

On my machine normally:

2408 ? S 0:00 /usr/local/pgsql/bin/postmaster -p 5432 -D /home/postgres/data
2615 ? S 0:00 postgres: stats buffer process
2616 ? S 0:00 postgres: stats collector process
2857 ? S 0:00 postgres: writer process
2858 ? S 0:00 postgres: stats buffer process
2859 ? S 0:00 postgres: stats collector process

But with an idle transaction:

2408 ? S 0:00 /usr/local/pgsql/bin/postmaster -p 5432 -D /home/postgres/data
2615 ? S 0:00 postgres: stats buffer process
2616 ? S 0:00 postgres: stats collector process
2857 ? S 0:00 postgres: writer process
2858 ? S 0:00 postgres: stats buffer process
2859 ? S 0:00 postgres: stats collector process
8679 ? S 0:00 postgres: smarlowe test [local] idle in transaction

Thar she blows!

Also, you can restart the database and vacuum it then too. Of course,
don't do that during regular business hours...

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Have a burning question? Go to Yahoo! Answers and get answers from real people who know. --0-1348166326-1165450766=:59076--