pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kevin Kempter <kevin@kevinkempterllc.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: determining which table is being vacuumed by autovacuum
Date: Thu, 23 Aug 2007 00:10:05 -0400
Message-ID: <16624.1187842205@sss.pgh.pa.us> (raw)
In-Reply-To: <200708221525.45292.kevin@kevinkempterllc.com>
References: <200708221525.45292.kevin@kevinkempterllc.com>

Kevin Kempter <kevin@kevinkempterllc.com> 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



view thread (3+ messages)  latest in thread

Message-ID: <16624.1187842205@sss.pgh.pa.us>
Permalink:  ../16624.1187842205@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/16624.1187842205@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, kevin@kevinkempterllc.com
  Subject: Re: determining which table is being vacuumed by autovacuum
  In-Reply-To: <16624.1187842205@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox