> On 16 Aug 2022, at 12:17, PG Doc comments form 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?
> Do you distinguish between lower and uppercase? Or do you consider all
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/14/pgtrgm.html
Description:
Hey guys,
I have a question regarding the trigram algorithm and I can not find any
information about it in your documentation:
Do you distinguish between lower
Op 16-08-2022 om 12:36 schreef Daniel Gustafsson:
On 16 Aug 2022, at 12:17, PG Doc comments form 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
> On 16 Aug 2022, at 12:54, Erik Rijkers wrote:
>
> Op 16-08-2022 om 12:36 schreef Daniel Gustafsson:
>>> On 16 Aug 2022, at 12:17, PG Doc comments form
>>> wrote:
>>> I have a question regarding the trigram algorithm and I can not find any
>>> information about it in your documentation:
>>
>
> Hello %
>
> The PostgreSQL pdf (A4) shows 12.11 instead of 12.12
>
> https://www.postgresql.org/files/documentation/pdf/12/postgresql-12-A4
> .pdf
>
>
>This link shows 12.12 for me. Perhaps you have some cache in your browser that
>needs to be cleared?
>//Magnus
Thanks Magnus. It was indeed
On Tue, Aug 16, 2022 at 7:48 AM William Sescu (Suva)
wrote:
>
> Hello %
>
>
>
> The PostgreSQL pdf (A4) shows 12.11 instead of 12.12
>
>
>
> https://www.postgresql.org/files/documentation/pdf/12/postgresql-12-A4.pdf
>
>
This link shows 12.12 for me. Perhaps you have some cache in your
browser
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 <
dan...@yesql.se>:
> > On 16 Aug 2022, at 12:54, Erik Rijkers wrote:
> >
> >
Op 16-08-2022 om 13:46 schreef Daniel Gustafsson:
On 16 Aug 2022, at 12:54, Erik Rijkers wrote:
Op 16-08-2022 om 12:36 schreef Daniel Gustafsson:
On 16 Aug 2022, at 12:17, PG Doc comments form wrote:
I have a question regarding the trigram algorithm and I can not find any
information about
Erik Rijkers writes:
> (bluntly stating 'similarity comparisons are case-insensitive' -
> although I'm not really sure..)
Perhaps like "similarity comparisons are case-insensitive in a
standard build of pg_trgm", if you want to nod to the existence
of a compile option without going into detail.
> On 16 Aug 2022, at 15:53, Tom Lane wrote:
>
> Erik Rijkers writes:
>> (bluntly stating 'similarity comparisons are case-insensitive' -
>> although I'm not really sure..)
>
> Perhaps like "similarity comparisons are case-insensitive in a
> standard build of pg_trgm", if you want to nod to
Daniel Gustafsson writes:
> Looking at this I'm leaning towards paring down the diff posted upthread with
> pretty much this, I think that will provide value while avoid causing
> confusion.
WFM.
> As a related side note, there are four instances of "case insensitive{ly}" in
> the docs with all
https://www.postgresql.org/docs/devel/sql-insert.html#id-1.9.3.152.9
Insert a distributor, or do nothing for rows proposed for insertion when an
> existing, excluded row (a row with a matching constrained column or columns
> after before row insert triggers fire) exists. Example assumes a unique
On Tue, Dec 7, 2021 at 02:28:09PM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/13/sql-set.html
> Description:
>
> Documentation for the set time zone command can be clearer. What it says for
>
Added a missing word:
Insert a distributor, or do nothing if the proposed row conflicts with an
existing row. Per-row triggers BEFORE INSERT are fired, and possible
effects on the proposed row applied, before checking for conflicts. Example
assumes a unique index on the did column exists:
Seeing that an earlier, related passage in the text reads:
> Note that the effects of all per-row BEFORE INSERT triggers are reflected
in excluded values, ...
I update my suggestion to use the same expression:
Insert a distributor, or do nothing if the proposed row conflicts with an
existing
Bruce Momjian writes:
> I have written the attached patch to mention this issue about sql_body
> functions.
Spell-check, please. Seems OK otherwise.
regards, tom lane
On Sat, Dec 25, 2021 at 02:36:27PM +, Erki Eessaar wrote:
>
> Hello
>
> PostgreSQL 14 added the feature: "Allow SQL-language functions and procedures
> to use SQL-standard function bodies."
>
> If I understand correctly, then in this case the system will track
> dependencies between tables
Sounds good to me.
Am Di., 16. Aug. 2022 um 15:53 Uhr schrieb Tom Lane :
> Erik Rijkers writes:
> > (bluntly stating 'similarity comparisons are case-insensitive' -
> > although I'm not really sure..)
>
> Perhaps like "similarity comparisons are case-insensitive in a
> standard build of
On Tue, Aug 16, 2022 at 03:34:22PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > I have written the attached patch to mention this issue about sql_body
> > functions.
>
> Spell-check, please. Seems OK otherwise.
Just when I think I didn't add enough text to warrant a spell check.
:-(
19 matches
Mail list logo
