Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 44E229F9900 for ; Thu, 23 Aug 2007 14:31:24 -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 77519-01 for ; Thu, 23 Aug 2007 14:31:14 -0300 (ADT) X-Greylist: delayed 00:06:39.522253 by SQLgrey-1.7.5 Received: from outbound-mail-56.bluehost.com (outbound-mail-56.bluehost.com [69.89.20.36]) by postgresql.org (Postfix) with SMTP id B6C899FA629 for ; Thu, 23 Aug 2007 14:31:08 -0300 (ADT) Received: (qmail 11572 invoked by uid 0); 23 Aug 2007 17:24:27 -0000 Received: from unknown (HELO box54.bluehost.com) (69.89.20.54) by mailproxy3.bluehost.com with SMTP; 23 Aug 2007 17:24:27 -0000 Received: from rrcs-71-41-16-51.sw.biz.rr.com ([71.41.16.51] helo=[10.0.12.106]) by box54.bluehost.com with esmtp (Exim 4.66) (envelope-from ) id 1IOGPw-0007Ve-OL for pgsql-admin@postgresql.org; Thu, 23 Aug 2007 11:24:25 -0600 From: Kevin Kempter To: pgsql-admin@postgresql.org Subject: Re: determining which table is being vacuumed by autovacuum (SOLVED) Date: Thu, 23 Aug 2007 11:23:40 -0600 User-Agent: KMail/1.9.7 References: <200708221525.45292.kevin@kevinkempterllc.com> <16624.1187842205@sss.pgh.pa.us> In-Reply-To: <16624.1187842205@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200708231123.40357.kevin@kevinkempterllc.com> X-Identified-User: {840:box54.bluehost.com:kevinkem:kevinkempterllc.com} {sentby:bopbeforesmtp 71.41.16.51 authed with ossfusion.com} X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.196 tagged_above=0 required=5 tests=AWL=0.935, BAYES_20=-0.74 X-Spam-Level: X-Archive-Number: 200708/296 X-Sequence-Number: 26627 On Wednesday 22 August 2007 22:10:05 Tom Lane wrote: > Kevin Kempter writes: > > Then I ran this: > > > > postgres=# select relation from pg_locks where pid = 9902; > > relation > > ----------- > > 82097999 > > 143763216 > > 143763215 > > 143763193 > > 143763193 > > 143763217 > > (7 rows) > > > > However none of these seem to have a corresponding pg_class oid, see > > the below queries: > > This most likely means that the vacuum is happening in a different > database than you are looking in. Did you check > pg_stat_activity.datname? > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster I sent this once but it never showed up on the list, so just to make sure it gets into the archives here it is again: All; I had a brain-dead moment (user-error). It turns out that the above queries do work fine when they're both run against the same database.