Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 7CBD69FA1C1 for ; Thu, 23 Aug 2007 01:10:26 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 95701-03 for ; Thu, 23 Aug 2007 01:10:20 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 1B8B99FA1B6 for ; Thu, 23 Aug 2007 01:10:19 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l7N4A59K016625; Thu, 23 Aug 2007 00:10:06 -0400 (EDT) To: Kevin Kempter cc: pgsql-admin@postgresql.org Subject: Re: determining which table is being vacuumed by autovacuum In-reply-to: <200708221525.45292.kevin@kevinkempterllc.com> References: <200708221525.45292.kevin@kevinkempterllc.com> Comments: In-reply-to Kevin Kempter message dated "Wed, 22 Aug 2007 15:25:45 -0600" Date: Thu, 23 Aug 2007 00:10:05 -0400 Message-ID: <16624.1187842205@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/282 X-Sequence-Number: 26613 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