From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Subject: Re: many animals are running old clients
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: buildfarm-members@postgresql.org
References: <144264ec-fd45-80eb-7642-109f920286b9@2ndQuadrant.com>
 <32103.1534542673@sss.pgh.pa.us>
Message-ID: <d1edfb5e-0bd7-838d-1b65-41c3886387ce@2ndQuadrant.com>
Date: Fri, 17 Aug 2018 19:57:07 -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: <32103.1534542673@sss.pgh.pa.us>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-MW
Precedence: bulk


On 08/17/2018 05:51 PM, Tom Lane wrote:
> Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
>> The majority of buildfarm animals are not on the latest client code
>> release. Version 8 was released more than 3 months ago. There are 26
>> animals on release 7 and 43 on even older releases, in one case on a
>> release going back 4 years. See below for the lists of delinquents.
> There's also a depressingly large number of animals that still aren't
> building the REL_11_STABLE branch.  Some also have odd gaps in their
> back-branch coverage.  If you don't use run_branches.pl to automate
> branch selection, please also take the time to check that you are
> building the right set of branches.
>
>> If this situation doesn't improve I'm going to have to reinstitute the
>> server filters which will reject very old clients.
> While I'd certainly encourage people to update, I'm not sure why
> that's necessary?


Example: Some animals are still getting the Pre_run_port_check error. 
That doesn't even exist any more, it disappeared when the security 
enhancements went in.


cheers

andrew

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