Re: issue in the doc

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Yousef Mohamed <yousssef(dot)mohammmed(dot)12(at)gmail(dot)com>
Cc: "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org>
Subject: Re: issue in the doc
Date: 2026-04-05 23:00:03
Message-ID: CAKFQuwZne4AfBc379r+FNq1gJ0SMmNKZzcvJ6pFZso5-OfbP4w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Sunday, April 5, 2026, Yousef Mohamed <yousssef(dot)mohammmed(dot)12(at)gmail(dot)com>
wrote:
>
> Question:
>
> In the expression:
> to_tsvector(x) @@ plainto_tsquery(y)
>
> what do x and y refer to exactly?
>
Local variables for the single expression being described. x is a text
typed value capable of being parsed as a vector, y is a text typed value
capable of being parsed as a query. (Or unknown, which then defaults to
text.).

>
> are they correspond to the left-hand and right-hand sides of the original
> expression (text @@ text) ?
>
In that x comes before y in the English alphabet just like in that
left-to-right language left comes physically before right, yes.

(text @@ text) isn’t an expression, it’s one’s way of writing the name of a
type.

if yes , i think it's better to mention the order of the x and y like :
> (x @@ y ) or ( y @@ x)
>
I’m not following how you think this could be improved. I get it’s very
western-centric, and admit it took me a moment to understand, but once I
did it seems quite clear to me. A concrete change to consider would be
helpful if this still doesn’t make sense. I have a few thoughts of my own,
chief among them being using real examples, but it doesn’t really my
threshold to work on at this time.

David J.

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Fujii Masao 2026-04-06 04:51:29 Re: doc: Clarify ANALYZE VERBOSE output
Previous Message Yousef Mohamed 2026-04-05 22:38:17 issue in the doc