| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: psql - add SHOW_ALL_RESULTS option |
| Date: | 2021-07-23 07:56:41 |
| Message-ID: | CAFj8pRAeXeKnuZKQCrMSqFGqZ2anNOV2uLg61i-rMAujxwTAog@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
pá 23. 7. 2021 v 9:41 odesílatel Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> napsal:
>
> >>> I tested manually for the pager feature, which mostly work, althoug
> >>> "pspg --stream" does not seem to expect two tables, or maybe there is
> >>> a way to switch between these that I have not found.
> >>
> >> pspg doesn't support this feature.
>
> Sure. Note that it is not a feature yet:-)
>
> ISTM that having some configurable pager-targetted marker would greatly
> help parsing on the pager side, so this might be the way to go, if this
> finally becomes a feature.
>
yes, It can help me lot of, and pspg can be less sensitive (or immune)
against synchronization errors.
Pavel
> --
> Fabien.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2021-07-23 08:30:23 | Re: proposal: enhancing plpgsql debug API - returns text value of variable content |
| Previous Message | Fabien COELHO | 2021-07-23 07:41:05 | Re: psql - add SHOW_ALL_RESULTS option |