Re: Better way of dealing with pgstat wait timeout during buildfarm runs?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Better way of dealing with pgstat wait timeout during buildfarm runs?
Date: 2014-12-28 01:51:47
Message-ID: 5969.1419731507@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Sat, Dec 27, 2014 at 7:55 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> This would have the effect of transferring all responsibility for
>> dead-stats-entry cleanup to autovacuum. For ordinary users, I think
>> that'd be just fine. It might be less fine though for people who
>> disable autovacuum, if there still are any.

> -1. I don't think it's a good idea to inflict pain on people who want
> to schedule their vacuums manually (and yes, there are some) to get
> clean buildfarm runs.

Did you read the rest of it?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-12-28 03:06:19 Re: nls and server log
Previous Message Robert Haas 2014-12-28 01:45:22 Re: Better way of dealing with pgstat wait timeout during buildfarm runs?