Re: WIP patch for avoiding duplicate initdb runs during "make check"

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WIP patch for avoiding duplicate initdb runs during "make check"
Date: 2017-07-03 13:21:51
Message-ID: CAB7nPqQH-J8QM9C4bf1qNbRrxJ4e4fhDRUCzo9i0qJTytgjC1w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 3, 2017 at 10:02 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Tom Lane wrote:
>
>> (Other unfinished work: teaching the MSVC scripts to use this,
>> and teaching pg_upgrade's test script to use it.)
>
> Maybe it'd be simpler to rewrite pg_upgrade tests using PostgresNode
> instead?

You are looking for this patch:
https://commitfest.postgresql.org/14/1101/
And for this thread:
https://www.postgresql.org/message-id/flat/CAB7nPqRdaN1A1YNjxNL9T1jUEWct8ttqq29dNv8W_o37+e8wfA(at)mail(dot)gmail(dot)com
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Euler Taveira 2017-07-03 13:23:27 Re: user-based query white list
Previous Message Michael Paquier 2017-07-03 13:20:36 Re: Error while copying a large file in pg_rewind