| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "Seki, Eiji" <seki(dot)eiji(at)jp(dot)fujitsu(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [Doc fix] Wrong explanation about tsquery_phrase |
| Date: | 2017-03-02 10:01:25 |
| Message-ID: | CA+TgmoYf7RR8D6kMrNFxOx-WF1LzykVgedGLKOOp9iNpufLShw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 28, 2017 at 3:24 PM, Seki, Eiji <seki(dot)eiji(at)jp(dot)fujitsu(dot)com> wrote:
> I found a wrong explanation about tsquery_phrase. I was slightly confused when I tried to use it.
>
> The current document explains tsquery_phrase as the followings[1].
>
> - Function: tsquery_phrase(query1 tsquery, query2 tsquery, distance integer)
> - Return Type: tsquery
> - Description: make query that searches for query1 followed by query2 at maximum distance distance
>
> However, 'exact distance' seems to be right instead of 'maximum distance'.
>
> This was probably overlooked in the following commit.
>
> 028350f619f7688e0453fcd2c4b25abe9ba30fa7
I think you are correct.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2017-03-02 10:04:51 | Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless) |
| Previous Message | Robert Haas | 2017-03-02 09:59:28 | Re: Documentation improvements for partitioning |