| From: | "Sven R(dot) Kunze" <srkunze(at)mail(dot)de> |
|---|---|
| To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, obartunov(at)gmail(dot)com, Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
| Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] few fts functions for jsonb |
| Date: | 2017-04-03 18:44:08 |
| Message-ID: | 98dfb391-d057-e78c-6248-0a3dc2f9e442@mail.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 01.04.2017 22:20, Andrew Dunstan wrote:
> I added documentation when I committed it for the new functions, in the
> FTS section. I'm not sure what we need to add to the JSON section if
> anything.
Not sure, if this is related but the formatting of
https://www.postgresql.org/docs/devel/static/functions-textsearch.html
looks a bit strange.
Just 2 questions/notes:
1) in what order are the values of the JSON extracted?
2) Regarding the additional line:
to_tsvector([ config regconfig , ] document json(b)) tsvector reduce
document text to tsvector to_tsvector('english', '{"a": "The Fat
Rats"}'::json) 'fat':2 'rat':3
Maybe change "reduce document text to tsvector" to "extracting JSON
values <in what order> and reduce to tsvector"?
Sven
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-04-03 18:44:20 | Re: Improve OR conditions on joined columns (common star schema problem) |
| Previous Message | Andres Freund | 2017-04-03 18:41:10 | Re: SERIALIZABLE with parallel query |