Date: Wed, 8 Jun 2022 12:16:22 +0200 (CEST)
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
cc: Tom Lane <tgl@sss.pgh.pa.us>,
    Alastair McKinley <a.mckinley@analyticsengines.com>,
    PostgreSQL Bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: psql 15beta1 does not print notices on the console until
 transaction completes
In-Reply-To: <4d4b752e-3cfb-494c-86db-27b48f347280@enterprisedb.com>
Message-ID: <alpine.DEB.2.22.394.2206081214410.1571886@pseudo>
References: 
 <PAXPR02MB760039506C87A2083AD85575E3DA9@PAXPR02MB7600.eurprd02.prod.outlook.com>
 <3662994.1653856025@sss.pgh.pa.us>
 <alpine.DEB.2.22.394.2205300849090.1166441@pseudo>
 <alpine.DEB.2.22.394.2205301921520.1376708@pseudo>
 <alpine.DEB.2.22.394.2205311331140.1672363@pseudo>
 <alpine.DEB.2.22.394.2206032001450.622878@pseudo>
 <4d4b752e-3cfb-494c-86db-27b48f347280@enterprisedb.com>
User-Agent: Alpine 2.22 (DEB 394 2020-01-19)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: 
 <https://www.postgresql.org/message-id/alpine.DEB.2.22.394.2206081214410.1571886%40pseudo>
Precedence: bulk


>> My short term recommendation is to remove the attempt at keeping the 
>> notice/result order for a tradeoff of getting the notices as soon as they 
>> are emitted, i.e. basically patch 1 and the acceptance of the diffs, called 
>> 1-bis in the attached.
>
> I agree with this solution.  Do you want to keep the tests, do you think they 
> are going to be stable?  I suppose we could try and find out.

I think that we should try to keep them, and remove them only if they are 
proven unstable, which may happen. The buildfarm will tell.

-- 
Fabien.