From: | Alexander Borisov <lex(dot)borisov(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Improve the performance of Unicode Normalization Forms. |
Date: | 2025-08-01 20:51:04 |
Message-ID: | ba965488-e2b2-4a62-af04-906818e453b1@gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
01.08.2025 23:37, Tom Lane пишет:
> Alexander Borisov <lex(dot)borisov(at)gmail(dot)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.
Thanks, Tom! I always choose optimism.
I've been in open source for a while, and this is the first time I've
seen this approach.
I have a plan to further improve Postgres performance in terms of
Unicode (and not only) (which is kind of the foundation for working with
text).
I don't want to overwhelm the community with patches. I take a
systematic approach.
Once again, thank you, Tom. The community's approach has become clearer.
--
Regards,
Alexander Borisov
From | Date | Subject | |
---|---|---|---|
Next Message | Melanie Plageman | 2025-08-01 20:57:50 | Re: Missing import in 035_standby_logical_decoding.pl |
Previous Message | Corey Huinker | 2025-08-01 20:35:15 | Re: pg_dump --with-* options |