On Tue, Sep 19, 2017 at 6:15 PM, Alvaro Herrera <alvhe...@alvh.no-ip.org> wrote: > Michael Paquier wrote: >> On Thu, Sep 7, 2017 at 11:14 AM, Michael Paquier >> <michael.paqu...@gmail.com> wrote: >> > Or we could make upgradecheck a noop, then remove it once all the MSVC >> > animals have upgraded to a newer version of the buildfarm client which >> > does not use upgradecheck anymore (I am fine to send a patch or a pull >> > request to Andrew for that). >> >> This patch is logged as "waiting on author" in the current commit >> fest, but any new patch will depend on the feedback that any other >> hacker has to offer based on the set of ideas I have posted upthread. >> Hence I am yet unsure what is the correct way to move things forward. >> So, any opinions? Peter or others? > > I think the first step is to send the rebased version of the patch. It > was last posted in April ...
Here you go. I have not done anything fancy for cross-version tests yet. -- Michael
pgupgrade-tap-test-v4.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
