| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, "Iwata, Aya" <iwata(dot)aya(at)jp(dot)fujitsu(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: psql - add SHOW_ALL_RESULTS option |
| Date: | 2019-07-25 21:42:11 |
| Message-ID: | alpine.DEB.2.21.1907252135060.21130@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bonsoir Daniel,
> FYI you forgot to remove that bit:
>
> + "SINGLELINE|SINGLESTEP|SHOW_ALL_RESULTS"))
Indeed. I found another such instance in "help.c".
> Also copydml does not seem to be exercised with combined
> queries, so do we need this chunk:
> --- a/src/test/regress/sql/copydml.sql
Yep, because I reorganized the notice code significantly, and I wanted to
be sure that the right notices are displayed in the right order, which
does not show if the trigger just says "NOTICE: UPDATE 8".
Attached a v2 for the always-show-all-results variant. Thanks for the
debug!
--
Fabien.
| Attachment | Content-Type | Size |
|---|---|---|
| psql-always-show-results-2.patch | text/x-diff | 33.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2019-07-25 21:50:57 | Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS) |
| Previous Message | Andres Freund | 2019-07-25 21:39:17 | Re: Server crash due to assertion failure in CheckOpSlotCompatibility() |