Skip site navigation (1) Skip section navigation (2)

Re: pgsql: Publish more openly the fact thatautovacuum is working for

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Publish more openly the fact thatautovacuum is working for
Date: 2008-07-22 13:19:17
Message-ID: 1216732757.3894.314.camel@ebony.2ndQuadrant (view raw or flat)
Thread:
Lists: pgsql-committers
On Mon, 2008-07-21 at 11:45 -0400, Tom Lane wrote:
> alvherre(at)postgresql(dot)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: wraparound_msg.v3.CVS_HEAD.patch
Description: text/x-patch (2.0 KB)

In response to

Responses

pgsql-committers by date

Next:From: Simon RiggsDate: 2008-07-22 19:07:44
Subject: Re: pgsql: Publish more openly the fact thatautovacuum is working for
Previous:From: User JbcooleyDate: 2008-07-22 05:15:09
Subject: npgsql - Npgsql2: quote identifiers when generating sql

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group