Re: Re: Better way of dealing with pgstat wait timeout during buildfarm runs? - Mailing list pgsql-hackers

From Noah Misch
Subject Re: Re: Better way of dealing with pgstat wait timeout during buildfarm runs?
Date
Msg-id 20150120011402.GB3149937@tornado.leadboat.com
Whole thread Raw
In response to Re: Re: Better way of dealing with pgstat wait timeout during buildfarm runs?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Jan 19, 2015 at 12:05:01PM -0500, Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
> > On Mon, Jan 19, 2015 at 11:30 AM, Andres Freund <andres@2ndquadrant.com> wrote:
> >> Sure, but the log isn't invisible. As mentioned one paragraph above, I
> >> don't think it's likely to ever be noticed in the client code in the
> >> cases where it happens in production.
> 
> > Yes, that is my feeling as well.
> 
> Meh.  I still don't like it, but I guess I'm outvoted.  Unless there are
> further votes, what we have at this point is just:
> 
> -        elog(WARNING, "pgstat wait timeout");
> +        ereport(LOG, (errmsg("using stale statistics instead of current ones because stats collector is not
responding")));
> 
> with no conditionality for pgstat_vacuum_stat vs. other callers.

That is satisfactory to me, too.



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: New CF app deployment
Next
From: Robert Haas
Date:
Subject: Re: B-Tree support function number 3 (strxfrm() optimization)