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

From Tom Lane
Subject Re: Re: Better way of dealing with pgstat wait timeout during buildfarm runs?
Date
Msg-id 27599.1421684921@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: Better way of dealing with pgstat wait timeout during buildfarm runs?  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Re: Better way of dealing with pgstat wait timeout during buildfarm runs?
List pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> On 2015-01-19 11:16:09 -0500, Tom Lane wrote:
>> Possibly we need to improve the wording of that error message then.
>> When it was written, we really assumed that it was a can't-happen case
>> and so didn't spend much effort on it.  Perhaps it should become a
>> translatable ereport phrased like "WARNING: using stale statistics
>> instead of current ones because stats collector is not responding".

> Yes, that seems like a good message improvement.

> It's not like making it LOG makes the message invisible...

Uh, yes it does.  So far as the user is concerned anyway.  The entire
point of this discussion is to prevent the message from showing up in
buildfarm output, remember?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Re: Better way of dealing with pgstat wait timeout during buildfarm runs?
Next
From: Andres Freund
Date:
Subject: Re: Re: Better way of dealing with pgstat wait timeout during buildfarm runs?