Re: autovacuum stuck on a table for 18+ hours, consuming lots of CPU time - Mailing list pgsql-general

From Tom Lane
Subject Re: autovacuum stuck on a table for 18+ hours, consuming lots of CPU time
Date
Msg-id 12410.1322020196@sss.pgh.pa.us
Whole thread Raw
In response to Re: autovacuum stuck on a table for 18+ hours, consuming lots of CPU time  (Lonni J Friedman <netllama@gmail.com>)
Responses Re: autovacuum stuck on a table for 18+ hours, consuming lots of CPU time  (Lonni J Friedman <netllama@gmail.com>)
List pgsql-general
Lonni J Friedman <netllama@gmail.com> writes:
> I suspect you're right.  I just ran strace against that PID again, and
> now all the lseek & read FD's are referrring to a different number
> (115), so that means its moved onto something new since I looked a few
> hours ago?

> Anyway, I think this is what you were referring to:
> /proc/30188/fd/115 ->   /var/lib/pgsql/data/base/64793/72633.10

> How do I correlate that file to an actual database object?

64793 is the pg_database.oid of the database, and 72633 is the
pg_class.relfilenode value of the table/index.

            regards, tom lane

pgsql-general by date:

Previous
From: Lonni J Friedman
Date:
Subject: Re: autovacuum stuck on a table for 18+ hours, consuming lots of CPU time
Next
From: Lonni J Friedman
Date:
Subject: Re: autovacuum stuck on a table for 18+ hours, consuming lots of CPU time