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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 22:35:33
Message-ID: CA+TgmoaApmPth0mdVJBo7JWxnEPod8t1UsNZo3HmJMyPxOmNNg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Dec 27, 2014 at 8:51 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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?

Yeah... since when do I not read your emails?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2014-12-28 23:19:11 Re: INSERT ... ON CONFLICT {UPDATE | IGNORE}
Previous Message Noah Misch 2014-12-28 21:58:31 Re: orangutan seizes up during isolation-check