Re: Improve the performance of Unicode Normalization Forms.
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Borisov <lex.borisov@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2025-08-01T19:37:02Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Use C11 char16_t and char32_t for Unicode code points.
- 3853a6956c3e 19 (unreleased) cited
Alexander Borisov <lex.borisov@gmail.com> writes: > I'm new here, so please advise me: if a patch wasn't accepted at the > commitfest, does that mean it's not needed (no one was interested in > it), or was there not enough time? It's kind of hard to tell really --- there are many patches in our queue and not nearly enough reviewers. So maybe someone will get to it in the fullness of time, or maybe it's true that no one cares about the particular topic. (But bug fixes and performance improvements are almost always interesting to someone.) I recommend optimism: as long as *you* still believe that the patch is worthwhile, keep pushing it forward to the next commitfest. We used to do that automatically, but we have started asking authors to do that themselves, as a way of weeding out patches for which the author has lost interest. regards, tom lane