| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, "Bossart, Nathan" <bossartn(at)amazon(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, "shiy(dot)fnst(at)fujitsu(dot)com" <shiy(dot)fnst(at)fujitsu(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-04-15 18:06:59 |
| Message-ID: | 451a2111-3757-c511-9413-8f8af531a167@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 15.04.21 13:51, Fabien COELHO wrote:
>>> That's a lot IMO, so my vote would be to discard this feature for now
>>> and revisit it properly in the 15 dev cycle, so as resources are
>>> redirected into more urgent issues (13 open items as of the moment of
>>> writing this email).
>>
>> I don't wish to tell people which open issues they ought to work on
>> ... but this patch seems like it could be quite a large can of worms,
>> and I'm not detecting very much urgency about getting it fixed.
>> If it's not to be reverted then some significant effort needs to be
>> put into it soon.
>
> My overly naive trust in non regression test to catch any issues has
> been largely proven wrong. Three key features do not have a single
> tests. Sigh.
>
> I'll have some time to look at it over next week-end, but not before.
I have reverted the patch and moved the commit fest entry to CF 2021-07.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthias van de Meent | 2021-04-15 18:47:26 | ATTACH PARTITION locking documentation for DEFAULT partitions |
| Previous Message | Matthias van de Meent | 2021-04-15 18:06:34 | Iterating on IndexTuple attributes and nbtree page-level dynamic prefix truncation |