| From: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
|---|---|
| To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Cc: | Arthur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru>, Oleg Bartunov <obartunov(at)postgrespro(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: json(b)_to_tsvector with numeric values |
| Date: | 2018-04-04 11:27:16 |
| Message-ID: | CA+q6zcVL4p7u6hEBwzsQJxPyRCLhbqjb_DTDcqqxc3raMo+Yhg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 4 April 2018 at 11:52, Teodor Sigaev <teodor(at)sigaev(dot)ru> wrote:
>>>> the consistency of FTS.I think this is a bug, which needs to be fixed,
>>>> else inconsistency with existing full text search will be gets
>>>> deeper.
>
> Hm, seems, it's useful feature, but I suggest to make separate function
> jsonb_any_to_tsvector and add support for boolean too (if you know better
> name for function, do not hide it). Changing behavior of existing function
> is not obvious for users and, seems, should not backpatched.
What do you think about having not a separate function, but a flag argument to
the existing one (like `create` in `jsonb_set`), that will have false as
default value? The result would be the same, but without an extra function with
almost the same implementation.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2018-04-04 11:47:11 | Re: Optimize Arm64 crc32c implementation in Postgresql |
| Previous Message | Heikki Linnakangas | 2018-04-04 11:21:21 | Re: Optimize Arm64 crc32c implementation in Postgresql |