Re: Replacing TAP test planning with done_testing()

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Michael Paquier <michael(at)paquier(dot)xyz>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Replacing TAP test planning with done_testing()
Date: 2022-02-11 20:28:00
Message-ID: 202202112028.we5v7c6f5hay@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2022-Feb-11, Tom Lane wrote:

> Andres Freund <andres(at)anarazel(dot)de> writes:

> > +1 on backpatching. Backpatching tests now is less likely to cause conflicts,
> > but more likely to fail during tests.
>
> If you've got the energy to do it, +1 for backpatching. I agree
> with Michael's opinion that doing so will probably save us
> future annoyance.

+1

--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2022-02-11 20:40:15 Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints
Previous Message Alvaro Herrera 2022-02-11 20:25:49 Re: support for MERGE