Re: pgsql: Publish more openly the fact that autovacuum is working for - Mailing list pgsql-committers

From Simon Riggs
Subject Re: pgsql: Publish more openly the fact that autovacuum is working for
Date
Msg-id 1216732757.3894.314.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: pgsql: Publish more openly the fact that autovacuum is working for  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Publish more openly the fact that autovacuum is working for  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-committers
On Mon, 2008-07-21 at 11:45 -0400, Tom Lane wrote:
> alvherre@postgresql.org (Alvaro Herrera) writes:
> > Publish more openly the fact that autovacuum is working for wraparound
> > protection.
>
> Now that I look more closely, there are two things I don't like about
> this patch:
>
> * it fails to ratchet up MAX_AUTOVAC_ACTIV_LEN to allow for the
> additional text
>
> * it produces something like
>
>     autovacuum: VACUUM (to prevent wraparound) foo.bar
>
> I had thought we were generating
>
>     autovacuum: VACUUM foo.bar (to prevent wraparound)
>
> which seems both easier to read and less likely to break any
> existing code that might be trying to interpret pg_stat_activity
> entries.

Ratcheted. Will do 8.3 change once approved.

--
 Simon Riggs           www.2ndQuadrant.com
 PostgreSQL Training, Services and Support

Attachment

pgsql-committers by date:

Previous
From: jbcooley@pgfoundry.org (User Jbcooley)
Date:
Subject: npgsql - Npgsql2: quote identifiers when generating sql
Next
From: Simon Riggs
Date:
Subject: Re: pgsql: Publish more openly the fact that autovacuum is working for