pg.ddx.io pgsql-hackers@postgresql.org mailing list archive help / color / mirror / Atom feed From: David Steele <david@pgmasters.net>
To: Alexander Korotkov <a.korotkov@postgrespro.ru>
Cc: Teodor Sigaev <teodor@sigaev.ru>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Jan Przemysław Wójcik <jan.przemyslaw.wojcik@gmail.com>
Cc: Postgres-Bugs <pgsql-bugs@postgresql.org>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: Fwd: [BUGS] pg_trgm word_similarity inconsistencies or bug
Date: Thu, 1 Mar 2018 19:12:25 -0500
Message-ID: <67add669-c41f-c115-5c1a-34a930da5a14@pgmasters.net> (raw )
In-Reply-To: <CAPpHfdvP+x54XuvTUoz85iSVHFW7dwLyEjya0SOMVz5tv-2dFQ@mail.gmail.com >
References: <CY4PR17MB13207ED8310F847CF117EED0D85A0@CY4PR17MB1320.namprd17.prod.outlook.com >
<20171028082225.GA2157@arthur.localdomain >
<CAPpHfdtz4a9dTxp-Fpem8uBdSBuOQV_i2xuFyL1tG6zM6nAkpg@mail.gmail.com >
<CA+YsLFp9scUNjjfYJC=84V9o-ZB66GWPq3e_Jveqs1bNejA4qA@mail.gmail.com >
<CAPpHfdsDtQJ+pYfapH7GMt9n4RLByKMzHEBWcPL99C_g+rkUKQ@mail.gmail.com >
<1510059095836-0.post@n3.nabble.com >
<CA+Tgmobksqi+Kh2=NZarEhnSUAudY=3oc+K8HjqSRvytbw7cnQ@mail.gmail.com >
<CAPpHfduRG6pXz8RC5TLppV7cpWeNPn0_4nNzX-nT4T6bb6_Y+Q@mail.gmail.com >
<CAPpHfdtXJp0xvi8QbcHWqnrk=XyyMux4FtbJCgZFPknPbLERVA@mail.gmail.com >
<42a3a2a4-59b9-c932-3bdf-e346e7b2e406@sigaev.ru >
<CAPpHfdv1oYVxCmLxyEGNH7vb3Fy2s0xHdv9R_NUy5EHecUqijQ@mail.gmail.com >
<CAPpHfdsfdC5L0xQ2QwshevbGnoL+L6Ex5B2eJq7FhSzFUqWg2Q@mail.gmail.com >
<708593ed-1104-a0d2-56b7-097adfdcfc16@pgmasters.net >
<CAPpHfdvP+x54XuvTUoz85iSVHFW7dwLyEjya0SOMVz5tv-2dFQ@mail.gmail.com >
Hi Alexander,
On 3/1/18 4:26 PM, Alexander Korotkov wrote:
> On Thu, Mar 1, 2018 at 11:05 PM, David Steele <david@pgmasters.net
> <mailto:david@pgmasters.net>> wrote:
>
> I agree with Teodor (upthread, not quoted here) that the documentation
> could use some editing.
>
> I started to do it myself, but quickly realized I have no knowledge of
> the content. I'm afraid I would destroy the meaning while updating the
> grammar.
>
> That's to problem. If you're willing to help you can edit the documentation
> and let me review that it's correct. Also feel free to ask any
> questions and
> more explanation from me. Ultimately, we need to have a documentation
> that any average user can understand, not to mention you :)
OK, I'm the CFM so I have my plate full for the next few days but if
nobody picks this up then I will give it a go.
> Anyone understand the subject matter well enough to review the
> documentation?
>
> I expect it would be hard to find anybody matching this criteria.
You are probably right, but it never hurts to try.
--
-David
david@pgmasters.net
view thread (28+ messages) latest in thread
Message-ID: <67add669-c41f-c115-5c1a-34a930da5a14@pgmasters.net>
Permalink: ../67add669-c41f-c115-5c1a-34a930da5a14@pgmasters.net/
Also on: postgresql.org/message-id/67add669-c41f-c115-5c1a-34a930da5a14@pgmasters.net
copy link · copy postgr.es
reply 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: david@pgmasters.net, a.korotkov@postgrespro.ru, teodor@sigaev.ru, robertmhaas@gmail.com, jan.przemyslaw.wojcik@gmail.com, pgsql-bugs@postgresql.org
Subject: Re: Fwd: [BUGS] pg_trgm word_similarity inconsistencies or bug
In-Reply-To: <67add669-c41f-c115-5c1a-34a930da5a14@pgmasters.net>
* 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