Andres Freund writes:
> On 2018-04-07 21:53:01 +0300, Teodor Sigaev wrote:
>> test select_parallel ... FAILED
>>
>> I don't understand how it's connected to json_to_tsquery. Can somebody point
>> me what I'm missing?
> Given that it "only" failed during upgrade check, not the earlie
Given that it "only" failed during upgrade check, not the earlier
parallel check, it is possible that it's entirely unrelated and just a
low likelihood event?
May be, may be. So, we have bug with low probability.
This however does clearly seem related:
https://buildfarm.postgresql.org/cgi-bin/s
On 2018-04-07 21:53:01 +0300, Teodor Sigaev wrote:
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=desmoxytes&dt=2018-04-07
> 18%3A32%3A02
>
> test select_parallel ... FAILED
>
> I don't understand how it's connected to json_to_tsquery. Can somebody point
> me what I'm miss
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=desmoxytes&dt=2018-04-07
18%3A32%3A02
test select_parallel ... FAILED
I don't understand how it's connected to json_to_tsquery. Can somebody
point me what I'm missing?
Teodor Sigaev wrote:
Add json(b)_to_tsvector function
Forget to add to test 'english' FTS configuration, will fix
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dunlin&dt=2018-04-07%2018%3A05%3A17
Teodor Sigaev wrote:
Add json(b)_to_tsvector function
Jsonb has a complex nature so there isn't best-for-everything way to convert it
to tsvect
Add json(b)_to_tsvector function
Jsonb has a complex nature so there isn't best-for-everything way to convert it
to tsvector for full text search. Current to_tsvector(json(b)) suggests to
convert only string values, but it's possible to index keys, numerics and even
booleans value. To solve that j
