Re: Lower or Upper case for F.33. pg_trgm

From: "Marc M(dot)" <marcmaiwald(at)googlemail(dot)com>
To: daniel(at)yesql(dot)se
Cc: Erik Rijkers <er(at)xs4all(dot)nl>, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Lower or Upper case for F.33. pg_trgm
Date: 2022-08-16 12:35:22
Message-ID: CANFdT3G1m6N5oWXwg3MZRtzGa8zfV+WOkX78fJvcj07BWyN5Tg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Thanks for your fast response.

Is this a question for me? I am fine with a short hint regarding the
default.
A link to another documentation is also fine.

Am Di., 16. Aug. 2022 um 13:46 Uhr schrieb Daniel Gustafsson <
daniel(at)yesql(dot)se>:

> > On 16 Aug 2022, at 12:54, Erik Rijkers <er(at)xs4all(dot)nl> wrote:
> >
> > Op 16-08-2022 om 12:36 schreef Daniel Gustafsson:
> >>> On 16 Aug 2022, at 12:17, PG Doc comments form <noreply(at)postgresql(dot)org>
> wrote:
> >>> I have a question regarding the trigram algorithm and I can not find
> any
> >>> information about it in your documentation:
> >> Maybe we should add something about this?
> >
> > Yeah, it's a bit strange that none of the following strings yield any
> info on that page: 'case', 'sensitiv', 'upper', 'lower', and that there is
> no mention of the ~ versus ~* difference.
> >
> > Maybe worth to (already in pgtrgm.html) give the simple hint:
> > ~ is case-sensitive
> > ~* is case-insensitive
> >
> > In any case a link to functions-matching.html seems indicated.
>
> Yeah, I think there is room for improvements here. Are you up for
> drafting a
> patch for this?
>
> --
> Daniel Gustafsson https://vmware.com/
>
>

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Erik Rijkers 2022-08-16 13:03:05 Re: Lower or Upper case for F.33. pg_trgm
Previous Message William Sescu (Suva) 2022-08-16 12:33:36 AW: PostgreSQL pdf shows 12.11 instead of 12.12