From: Alexander Borisov <lex.borisov@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Improve the performance of Unicode Normalization Forms.
Date: Fri, 1 Aug 2025 23:51:04 +0300
Message-ID: <ba965488-e2b2-4a62-af04-906818e453b1@gmail.com> (raw)
In-Reply-To: <2492580.1754077022@sss.pgh.pa.us>
References: <844d3dd7-2955-4794-95d1-7f4c13cb89fc@gmail.com>
<4211ffd7fe154c4af693b98d78f4a3689ce8cc30.camel@j-davis.com>
<16f87504-f174-450e-93cc-2db1074522bb@gmail.com>
<96c54fc3dde2ebaccafbd1ffa29b8be1005c8b8c.camel@j-davis.com>
<677cde50-6d64-474b-9ba8-bab380a111b3@gmail.com>
<599663a8d5948243bd87bf55a4f76bbb4a51a6e8.camel@j-davis.com>
<85f2a36f-f70a-4667-be48-49b652457295@gmail.com>
<088432f3-a3a9-4c40-8295-6c687c25d651@gmail.com>
<9db10eba-a756-4b3f-9550-83cab1a1a39e@gmail.com>
<2492580.1754077022@sss.pgh.pa.us>
01.08.2025 23:37, Tom Lane пишет:
> 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.
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: lex.borisov@gmail.com, tgl@sss.pgh.pa.us
Subject: Re: Improve the performance of Unicode Normalization Forms.
In-Reply-To: <ba965488-e2b2-4a62-af04-906818e453b1@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox