Re: 回复: cleanup: Split long Makefile lists across lines and sort them

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Japin Li <japinli(at)hotmail(dot)com>
Cc: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, 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-28 23:29:25
Message-ID: aVG9VUva4caD7Grf@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2025-12-28 23:53:16 Re: index prefetching
Previous Message Jelte Fennema-Nio 2025-12-28 23:25:22 Re: RFC: adding pytest as a supported test framework