On Sat, Apr 6, 2013 at 4:20 PM, Jeff Janes <jeff.janes@gmail.com> wrote:
> I've often wanted to know what the autovacuum worker was doing. The process
> title seems like the best place to get this information, but the process
> title tells me what database it is in, but not what table it is working on.
>
> The attached patch demonstrates the concept of what I want. I put the code
> in table_recheck_autovac not because I think that is the best location, but
> just because it was the easiest point at which I knew how to get the table
> name easily before classTup gets destroyed.
>
> Example output:
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 16392 jjanes 20 0 229m 19m 6948 S 3.6 1.0 0:06.85 postgres:
> autovacuum worker process jjanes.public.pgbench_accounts
>
> I never reset the process title back to the initial state of just having a
> database name and no table. Which I can get away with temporarily because
> the autovac worker never dilly-dallies between tables, it either goes to the
> next one, or exits. A real implementation would probably want to reset it
> anyway, though.
>
> Is this functionality something we want? If so should it include explicit
> vacuum as well as autovac? Any opinion about where in the code base it
> properly belongs (which obviously depends on whether it should cover manual
> vacuum as well)? And does the string need to distinguish between an autovac
> and an autoanalyze?
I'm not sure whether it's a good idea to do this for manual vacuum
(the answer may depend on what the code ends up looking like), but it
seems good to do it at least for autovac. I don't think it's
absolutely necessary to distinguish between autovac and autoanalyze,
but I think it would be nice. Generally, +1 for doing something along
these lines.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company