| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| 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-08 10:16:22 |
| Message-ID: | alpine.DEB.2.22.394.2206081214410.1571886@pseudo |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general |
>> 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Berg | 2022-06-08 13:07:57 | Fallout from 'Make type "name" collation-aware' and tg_table_name |
| Previous Message | David Rowley | 2022-06-08 00:41:17 | Re: BUG #17512: Process running query fails with SIGSEV - nodeMemoize.c:349 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim McNamara | 2022-06-08 10:51:29 | |
| Previous Message | Peter Adlersburg | 2022-06-08 07:59:06 | message log merge (streaming replication) |