From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Subject: Re: many animals are running old clients
To: Noah Misch <noah@leadboat.com>, buildfarm-members@postgresql.org
References: <144264ec-fd45-80eb-7642-109f920286b9@2ndQuadrant.com>
 <20180818070030.GA3795674@rfd.leadboat.com>
 <d6a8bb37-eb72-b663-7fa7-6fb8aaa5cb25@2ndQuadrant.com>
 <20180818162211.GC3795674@rfd.leadboat.com>
Message-ID: <966eeb24-3f37-29da-dee2-91522bbe1850@2ndQuadrant.com>
Date: Sun, 19 Aug 2018 15:04:58 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <20180818162211.GC3795674@rfd.leadboat.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-MW
Precedence: bulk


On 08/18/2018 12:22 PM, Noah Misch wrote (offlist):
> On Sat, Aug 18, 2018 at 08:17:17AM -0400, Andrew Dunstan wrote:
>>
>> Is there anything I can do to make upgrade easier?
> The show_log.pl web page could highlight a particular run's config change,
> including version number changes, when there is such a change compared to the
> previous run.  If it's clear enough that folks are unlikely to confuse an
> upgrade-induced failure with a PG-commit-induced failure, I could stop checking
> for post-upgrade buildfarm failures.


What I've done is add this to the database in a way that makes it easily 
accessible to the web app, and added that info to the history page.

I might break that out into a separate history at some stage.


>
> It wouldn't make an upgrade easier, but the "Flags" column of show_status.pl
> could give an extra badge for being on the latest version.  That would motivate
> some folks.


Yes, I'll look at this, although I'm reluctant to make the dashboard any 
more busy.


cheers

andrew

-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services