pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alastair McKinley <a.mckinley@analyticsengines.com>
Cc: PostgreSQL Bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: psql 15beta1 does not print notices on the console until transaction completes
Date: Thu, 9 Jun 2022 09:38:38 +0200
Message-ID: <1098ba35-3bea-6953-e9b0-d7fd516d5abd@enterprisedb.com> (raw)
In-Reply-To: <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>
	<alpine.DEB.2.22.394.2206081214410.1571886@pseudo>

On 08.06.22 12:16, Fabien COELHO wrote:
>>> 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.

Ok, committed as you submitted.






view thread (16+ messages)

Message-ID: <1098ba35-3bea-6953-e9b0-d7fd516d5abd@enterprisedb.com>
Permalink:  ../1098ba35-3bea-6953-e9b0-d7fd516d5abd@enterprisedb.com/
Also on:    postgresql.org/message-id/1098ba35-3bea-6953-e9b0-d7fd516d5abd@enterprisedb.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: peter.eisentraut@enterprisedb.com, coelho@cri.ensmp.fr, tgl@sss.pgh.pa.us, a.mckinley@analyticsengines.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: psql 15beta1 does not print notices on the console until transaction completes
  In-Reply-To: <1098ba35-3bea-6953-e9b0-d7fd516d5abd@enterprisedb.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox