On Mon, Dec 4, 2017 at 11:48 PM, Tom Lane wrote:
> Rudy Barbieri writes:
>> But it could be better improve the documentation highlighting that in
>> previous versions there was a bug.
>
> I see no bug here ... failing to recognize an operator that was added in
> later versions can hardly be class
Rudy Barbieri writes:
> But it could be better improve the documentation highlighting that in
> previous versions there was a bug.
I see no bug here ... failing to recognize an operator that was added in
later versions can hardly be classed as a bug.
regards, tom lane
Thanks for the tip!
But it could be better improve the documentation highlighting that in
previous versions there was a bug.
Il 03 dic 2017 5:40 PM, "David G. Johnston" ha
scritto:
> On Sunday, December 3, 2017, Tom Lane wrote:
>
>> barbiomalef...@gmail.com writes:
>> > I copied the text in the
On Sunday, December 3, 2017, Tom Lane wrote:
> barbiomalef...@gmail.com writes:
> > I copied the text in the followed by example: SELECT
> to_tsvector('fatal
> > error') @@ to_tsquery('fatal <-> error');
> > but it will always goes in error: ERROR: syntax error in tsquery:
> "fatal
> > <-> erro
barbiomalef...@gmail.com writes:
> I copied the text in the followed by example: SELECT to_tsvector('fatal
> error') @@ to_tsquery('fatal <-> error');
> but it will always goes in error: ERROR: syntax error in tsquery: "fatal
> <-> error"
> SQL state: 42601
The described symptoms sound like you'
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.6/static/textsearch-intro.html
Description:
I copied the text in the followed by example: SELECT to_tsvector('fatal
error') @@ to_tsquery('fatal <-> error');
but it will always goes in err
