| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-09 07:38:38 |
| Message-ID: | 1098ba35-3bea-6953-e9b0-d7fd516d5abd@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general |
On 08.06.22 12:16, 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.
>
> 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.
Ok, committed as you submitted.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-06-09 17:01:36 | Re: BUG #17514: Application with embedded SQL crashes when executing EXEC SQL PREPARE |
| Previous Message | PG Bug reporting form | 2022-06-09 06:40:28 | BUG #17514: Application with embedded SQL crashes when executing EXEC SQL PREPARE |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2022-06-09 07:51:25 | Re: message log merge (streaming replication) |
| Previous Message | Ian Lawrence Barwick | 2022-06-09 07:26:24 | Re: message log merge (streaming replication) |