On Thu, Aug 21, 2025 at 12:55 AM Jeff Davis wrote:
> On Mon, 2025-08-18 at 00:44 +0300, Alexander Korotkov wrote:
> > I'd like to propose a new version of patch.
>
> Nit: it only uses the title case in ICU or builtin PG_UNICODE_FAST.
Corrected, thank you. Any objec
e primary use case is for compatibility, then we might be
> trying to hard to make this a provider-specific feature.
I'd like to propose a new version of patch. It includes specification
of behavior for each locale provider including particular ICU
function. Also it saves the note from upt
On Wed, Jul 30, 2025 at 10:58 PM Jeff Davis wrote:
>
> On Mon, 2025-07-28 at 13:20 +0300, Alexander Korotkov wrote:
> > I can confirm inicap works with libc and libicu as you stated. The
> > documentation patch looks good to me. I’ve written a commit message.
> > The
e
> > want
> > in master.
>
> +1.
Done, reverted everywhere except master.
--
Regards,
Alexander Korotkov
Supabase
commit these extra improvements on top. Can you take care
> > of these follow-up patches? Or, just revert the change and I can make
> > the improvements in master.
>
> Yes, I was not in favor of backpatching this, since it was not a bug
> fix. And it turns out it was incomplete. I think we should revert all
> the backpatches and iterate on getting the documentation the way we want
> in master.
Got it. Sorry for the confusion. I'll revert patches from back
branches and then continue to work on the subject for master.
--
Regards,
Alexander Korotkov
Supabase
On Mon, Jul 28, 2025 at 1:20 PM Alexander Korotkov wrote:
>
> On 25 Sep 2024, at 18:13, Oleg Tselebrovskiy
> wrote:
>
> Greetings, everyone!
>
> One of our clients has found a difference in behaviour of initcap function
> when
> using different locale provider
Hi, Oleg!On 25 Sep 2024, at 18:13, Oleg Tselebrovskiy wrote:Greetings, everyone!One of our clients has found a difference in behaviour of initcap function whenusing different locale providers, shown below postgres=# create database test_db_1 locale_provider=icu locale="ru_RU.UTF-8" template=templa
On Tue, May 4, 2021 at 3:55 AM Bruce Momjian wrote:
> On Tue, May 4, 2021 at 03:51:51AM +0300, Alexander Korotkov wrote:
> > Hi, Bruce!
> >
> > On Tue, May 4, 2021 at 2:49 AM Bruce Momjian wrote:
> > > In patch "Handle equality operator in contrib/pg_trgm&
suggest the PG 14 mention be removed.
I agree with this. Thank you for pointing. Are you OK with the attached patch?
--
Regards,
Alexander Korotkov
pg_trgm_doc_fix.patch
Description: Binary data
On Thu, Sep 12, 2019 at 5:38 PM Alvaro Herrera wrote:
>
> On 2019-Sep-12, Alexander Korotkov wrote:
>
> > On Thu, Sep 12, 2019 at 4:58 PM Liudmila Mantrova
> > wrote:
> > > Please consider these small patches for REL_12_STABLE that mainly fix
> > > remai
t; operators with spaces in path definitions.
I'm going to push these two if no objections.
--
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
> + Bloom AM doesn't supports NULL values.
> >
> > s/supports/support/
These two were already fixed in the version I've pushed before.
--
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
On Wed, Jun 13, 2018 at 5:57 PM Bruce Momjian wrote:
> On Fri, Jun 1, 2018 at 06:39:11PM +0300, Alexander Korotkov wrote:
> > On Sat, May 26, 2018 at 7:56 PM Bruce Momjian wrote:
> >
> > While creating the release notes, I was confused by the description for
> >
On Fri, Jun 1, 2018 at 6:39 PM Alexander Korotkov wrote:
> On Sat, May 26, 2018 at 7:56 PM Bruce Momjian wrote:
>>
>> While creating the release notes, I was confused by the description for
>> strict_word_similarity(), particularly "extent boundaries". The
>&g
he strict_word_similarity(text, text)
function
!is useful for finding the similarity to whole words, while
word_similarity(text, text) is more suitable for
!finding the similarity for parts of words.
This also looks correct to me.
--
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
15 matches
Mail list logo
