From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alastair McKinley <a(dot)mckinley(at)analyticsengines(dot)com>, PostgreSQL Bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
Subject: | Re: psql 15beta1 does not print notices on the console until transaction completes |
Date: | 2022-05-30 09:05:48 |
Message-ID: | alpine.DEB.2.22.394.2205300849090.1166441@pseudo |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-general |
> Alastair McKinley <a(dot)mckinley(at)analyticsengines(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Guo | 2022-05-30 09:18:44 | Re: BUG #17502: View based on window functions returns wrong results when queried |
Previous Message | Michael Paquier | 2022-05-30 06:54:08 | Re: BUG #17485: Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY |
From | Date | Subject | |
---|---|---|---|
Next Message | Imre Samu | 2022-05-30 10:30:55 | Re: Is it possible to index "deep" into a JSONB column? |
Previous Message | Shaheed Haque | 2022-05-30 08:18:29 | Re: Is it possible to index "deep" into a JSONB column? |