Re: json(b)_to_tsvector with numeric values - Mailing list pgsql-hackers

From Dmitry Dolgov
Subject Re: json(b)_to_tsvector with numeric values
Date
Msg-id CA+q6zcVL4p7u6hEBwzsQJxPyRCLhbqjb_DTDcqqxc3raMo+Yhg@mail.gmail.com
Whole thread Raw
In response to Re: json(b)_to_tsvector with numeric values  (Teodor Sigaev <teodor@sigaev.ru>)
Responses Re: json(b)_to_tsvector with numeric values
List pgsql-hackers
> On 4 April 2018 at 11:52, Teodor Sigaev <teodor@sigaev.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.


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Optimize Arm64 crc32c implementation in Postgresql
Next
From: Thomas Munro
Date:
Subject: Re: Optimize Arm64 crc32c implementation in Postgresql