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: 2021-12-29 07:42:53
Message-ID: alpine.DEB.2.22.394.2112290832290.1019176@pseudo
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


>> [...]
>
> I agree that these two behaviors in libpq are dubious, especially the
> second one. I want to spend some time analyzing this more and see if
> fixes in libpq might be appropriate.

Ok.

My analysis is that fixing libpq behavior is not in the scope of a psql
patch, and that if I was to do that it was sure delay the patch even
further. Also these issues/features are corner cases that provably very
few people bumped into.

--
Fabien.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2021-12-29 09:46:52 Re: Foreign key joins revisited
Previous Message Dinesh Chemuduru 2021-12-29 07:39:29 Re: [PROPOSAL] new diagnostic items for the dynamic sql