Re: autovacuum stuck on a table for 18+ hours, consuming lots of CPU time

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Lonni J Friedman <netllama(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: autovacuum stuck on a table for 18+ hours, consuming lots of CPU time
Date: 2011-11-23 03:49:56
Message-ID: 12410.1322020196@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Lonni J Friedman <netllama(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Lonni J Friedman 2011-11-23 04:00:48 Re: autovacuum stuck on a table for 18+ hours, consuming lots of CPU time
Previous Message Lonni J Friedman 2011-11-23 03:43:58 Re: autovacuum stuck on a table for 18+ hours, consuming lots of CPU time