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
