Re: Is autovacuum doing a wraparound-avoiding VACUUM? - Mailing list pgsql-patches

From Simon Riggs
Subject Re: Is autovacuum doing a wraparound-avoiding VACUUM?
Date
Msg-id 1216454648.19656.798.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: Is autovacuum doing a wraparound-avoiding VACUUM?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Is autovacuum doing a wraparound-avoiding VACUUM?  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-patches
On Fri, 2008-07-18 at 01:44 -0400, Tom Lane wrote:
> Simon Riggs <simon@2ndquadrant.com> writes:
> > On Thu, 2008-07-17 at 17:10 -0400, Alvaro Herrera wrote:
> >> I don't like your wording though; it feels too verbose (and you're
> >> losing the ANALYZE in case it's doing both things).  How about
> >>
> >> snprintf(activity, MAX_AUTOVAC_ACTIV_LEN,
> >> "autovacuum: VACUUM%s%s", vac
> >> tab->at_doanalyze ? " ANALYZE" : "",
> >> tab->at_wraparound ? " (wraparound)" : "");
>
> > Yes, looks good.
>
> May I suggest "(to prevent wraparound)" or something like that?
> Otherwise, +1.
>
> >> You're not proposing it for 8.3 right?
>
> > I think I am. It's an important diagnostic for your other fix.
>
> I agree, this is important for visibility into what's happening.
> The string isn't getting translated so I don't see any big downside
> to applying the patch in back branches.

Patches for 8.3 and CVS HEAD.

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

Attachment

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: doc patch - archive/restore_command on windows
Next
From: Stephen Frost
Date:
Subject: pg_dump additional options for performance