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

From: Noah Misch <noah(at)leadboat(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, michael(at)otacoo(dot)com, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tomas Vondra <tv(at)fuzzy(dot)cz>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Better way of dealing with pgstat wait timeout during buildfarm runs?
Date: 2014-12-28 01:08:44
Message-ID: 20141228010844.GA2055615@tornado.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 25, 2014 at 09:14:36PM +0100, Andres Freund wrote:
> My guess is that a checkpoint happened at that time. Maybe it'd be a
> good idea to make pg_regress start postgres with log_checkpoints
> enabled? My guess is that we'd find horrendous 'sync' times.

+1, independent of $SUBJECT. How about log_autovacuum_min_duration=0, too?

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-12-28 01:36:27 Re: nls and server log
Previous Message Robert Haas 2014-12-28 01:05:42 Re: Misaligned BufferDescriptors causing major performance problems on AMD