| From: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Japin Li <japinli(at)hotmail(dot)com>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, zengman <zengman(at)halodbtech(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: cleanup: Split long Makefile lists across lines and sort them |
| Date: | 2025-12-29 01:50:35 |
| Message-ID: | 4D738BB6-A536-4F51-A6D3-50D899D70E78@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Dec 29, 2025, at 07:29, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Sun, Dec 28, 2025 at 04:12:16AM +0000, Japin Li wrote:
>> 2. I noticed that btree_gin, btree_gist, and pgcrypto also have relatively
>> long REGRESS lists, should we also update them?
>
> If we think about that in terms of frequency where new test files are
> added, it seems to me that there would be more meaning to do that for
> pgcrypto, test_decoding and pgss. This is more true for the two last
> entries of this list.
>
> About the rest? Not so much. Still, I was surprised to see that we
> have added stuff to btree_gist recently for WITHOUT OVERLAPS, so
> perhaps there is a point there.
> --
> Michael
This patch reminded me an old technique of using ENDLIST to terminate mule-line lists in Makefile. I started a new thread for that. Please see the details in [1].
Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-12-29 02:03:39 | Re: [PROPOSAL] Termination of Background Workers for ALTER/DROP DATABASE |
| Previous Message | Henson Choi | 2025-12-29 01:46:26 | Re: RFC: PostgreSQL Storage I/O Transformation Hooks |