Re: psql - add SHOW_ALL_RESULTS option

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: coelho(at)cri(dot)ensmp(dot)fr
Cc: daniel(at)manitou-mail(dot)org, peter(dot)eisentraut(at)2ndquadrant(dot)com, iwata(dot)aya(at)jp(dot)fujitsu(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: psql - add SHOW_ALL_RESULTS option
Date: 2019-07-26 04:17:04
Message-ID: 20190726.131704.86173346.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello.

At Thu, 25 Jul 2019 21:42:11 +0000 (GMT), Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> wrote in <alpine(dot)DEB(dot)2(dot)21(dot)1907252135060(dot)21130(at)lancre>
>
> 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!

I have some comments on this patch.

I'm +1 for always output all results without having knobs.

Documentation (psql-ref.sgml) has another place that needs the
same amendment.

Looking the output for -t, -0, -A or something like, we might need
to introduce result-set separator.

# -eH looks broken for me but it would be another issue.

Valid setting of FETCH_COUNT disables this feature. I think it is
unwanted behavior.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2019-07-26 04:18:01 pqParseInput3 overruns
Previous Message Amit Kapila 2019-07-26 04:13:24 Re: SegFault on 9.6.14