From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alastair McKinley <a.mckinley@analyticsengines.com>
Cc: pgsql-bugs@lists.postgresql.org, Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>
Subject: Re: psql 15beta1 does not print notices on the console until transaction completes
Date: Sun, 29 May 2022 16:27:05 -0400
Message-ID: <3662994.1653856025@sss.pgh.pa.us> (raw)
In-Reply-To: <PAXPR02MB760039506C87A2083AD85575E3DA9@PAXPR02MB7600.eurprd02.prod.outlook.com>
References: <PAXPR02MB760039506C87A2083AD85575E3DA9@PAXPR02MB7600.eurprd02.prod.outlook.com>
[ redirecting to -bugs ]
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).
I agree it's pretty undesirable, so I'm adding it as an open issue.
regards, tom lane
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: tgl@sss.pgh.pa.us, a.mckinley@analyticsengines.com, peter.eisentraut@enterprisedb.com, coelho@cri.ensmp.fr
Subject: Re: psql 15beta1 does not print notices on the console until transaction completes
In-Reply-To: <3662994.1653856025@sss.pgh.pa.us>
* 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