Re: psql - add SHOW_ALL_RESULTS option

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: "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: 2022-03-12 16:27:48
Message-ID: alpine.DEB.2.22.394.2203121726590.3679190@pseudo
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

>> Are you planning to send a rebased patch for this commit fest?
> Argh, I did it in a reply in another thread:-( Attached v15.
> So as to help moves things forward, I'd suggest that we should not to care
> too much about corner case repetition of some error messages which are due to
> libpq internals, so I could remove the ugly buffer reset from the patch and
> have the repetition, and if/when the issue is fixed later in libpq then the
> repetition will be removed, fine! The issue is that we just expose the
> strange behavior of libpq, which is libpq to solve, not psql.

See attached v16 which removes the libpq workaround.


Attachment Content-Type Size
psql-show-all-results-16.patch text/x-diff 48.2 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-03-12 20:15:17 Re: Issue with pg_stat_subscription_stats
Previous Message Justin Pryzby 2022-03-12 16:12:26 Re: preserving db/ts/relfilenode OIDs across pg_upgrade (was Re: storing an explicit nonce)