Date: Mon, 30 May 2022 11:05:48 +0200 (CEST)
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Tom Lane <tgl@sss.pgh.pa.us>
cc: Alastair McKinley <a.mckinley@analyticsengines.com>,
    PostgreSQL Bugs <pgsql-bugs@lists.postgresql.org>,
    Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Subject: Re: psql 15beta1 does not print notices on the console until
 transaction completes
In-Reply-To: <3662994.1653856025@sss.pgh.pa.us>
Message-ID: <alpine.DEB.2.22.394.2205300849090.1166441@pseudo>
References: 
 <PAXPR02MB760039506C87A2083AD85575E3DA9@PAXPR02MB7600.eurprd02.prod.outlook.com>
 <3662994.1653856025@sss.pgh.pa.us>
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.2205300849090.1166441%40pseudo>
Precedence: bulk


> Alastair McKinley <a.mckinley@analyticsengines.com> writes:
>> Using this test function:
>
>>     create or replace function test_notice() returns void as
>>     $$
>>     begin
>>         raise notice 'hello';
>>         perform pg_sleep(10);
>>     end; $$ language plpgsql;
>
>> In psql 15beta1, the "hello" message only appears on the console when the transaction completes.
>> in psql 14.3, it appears immediately as I would have expected.
>
> A quick cross-check confirms that this is a psql, not server,
> behavior change.  I didn't bisect, but I'm betting this is a
> side-effect of 7844c9918 (Show all query results by default).

Yep, that is indeed possible, there is some hocus-pocus around notices 
there because they arrive somehow in any order.

> I agree it's pretty undesirable, so I'm adding it as an open issue.

Ok.

-- 
Fabien.