Re: psql 15beta1 does not print notices on the console until transaction completes

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, 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>
Subject: Re: psql 15beta1 does not print notices on the console until transaction completes
Date: 2022-06-07 12:05:32
Message-ID: 4d4b752e-3cfb-494c-86db-27b48f347280@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-general

On 03.06.22 20:25, 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.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Aleš Zelený 2022-06-07 17:04:38 Re: BUG #17512: Process running query fails with SIGSEV - nodeMemoize.c:349
Previous Message Aleš Zelený 2022-06-07 08:29:31 Re: BUG #17512: Process running query fails with SIGSEV - nodeMemoize.c:349

Browse pgsql-general by date

  From Date Subject
Next Message Ц 2022-06-07 13:11:29 SQL state: 42601. Execption handling.
Previous Message Niels Jespersen 2022-06-07 05:43:48 SV: GSSAPI authentication