From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Kevin Kempter <kevink(at)consistentstate(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: pg_stat_activity reporting of VACUUM in 8.1 |
Date: | 2009-07-24 16:58:43 |
Message-ID: | 20090724165843.GD15591@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Kevin Kempter wrote:
> Hi all;
>
> looking at a system running 8.1.15
> via a select from pg_stat_activity I see a row where the vcurrent_query =
> 'VACUUM'
>
> I see also that autovacuum is on. Would autovacuum be running a vacuum on the
> entire db? I didn't think autovacuum did that. If not, how do I know in
> version 8.1 what table is being vacuumed? I thought that even in 8.1 the
> current_query column in pg_stat_activity would list the full sql being run as
> opposed to 'VACUUM'.
It might need to run database wide vacuum in case of transaction
wraparound.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Carol Walter | 2009-07-24 17:39:56 | Re: Cannot connect to postgresql |
Previous Message | Julius Tuskenis | 2009-07-24 07:07:13 | Re: Cannot connect to postgresql |