| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql - pager support - using invisible chars for signalling end of report |
| Date: | 2020-04-25 00:19:28 |
| Message-ID: | CAKFQuwZsof8Ebq+VExK+CbQ3ewLXnqk13dXGLnSgQgf_eQAL_g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Apr 24, 2020 at 5:12 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> > pá 24. 4. 2020 v 21:33 odesílatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:
> >> And what will happen when those characters are in the data?
>
> > It will be used on pager side as signal so previous rows was really last
> > row of result, and new row will be related to new result.
>
> In other words, it will misbehave badly if those characters appear
> in the query result. Doesn't sound acceptable to me.
>
Random thought but NUL isn't allowed in data so could it be used as a
protocol flag?
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-04-25 00:29:48 | Re: Setting min/max TLS protocol in clientside libpq |
| Previous Message | Tom Lane | 2020-04-25 00:12:25 | Re: psql - pager support - using invisible chars for signalling end of report |