Re: psql 15beta1 does not print notices on the console until transaction completes - Mailing list pgsql-bugs

From Fabien COELHO
Subject Re: psql 15beta1 does not print notices on the console until transaction completes
Date
Msg-id alpine.DEB.2.22.394.2206081214410.1571886@pseudo
Whole thread Raw
In response to Re: psql 15beta1 does not print notices on the console until transaction completes  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: psql 15beta1 does not print notices on the console until transaction completes  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-bugs
>> 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.

-- 
Fabien.



pgsql-bugs by date:

Previous
From: David Rowley
Date:
Subject: Re: BUG #17512: Process running query fails with SIGSEV - nodeMemoize.c:349
Next
From: Christoph Berg
Date:
Subject: Fallout from 'Make type "name" collation-aware' and tg_table_name