Re: BUG #8970: ts_parse incorrectly split numbers in digit token

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Marco Atzeri <marco(dot)atzeri(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #8970: ts_parse incorrectly split numbers in digit token
Date: 2014-01-26 17:27:16
Message-ID: 3433.1390757236@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Marco Atzeri <marco(dot)atzeri(at)gmail(dot)com> writes:
> On 26/01/2014 03:25, Alvaro Herrera wrote:
>> To trace this, I would look at src/backend/tsearch/wparser_def.c;
>> probably try compiling that file with WPARSER_TRACE defined, and compare
>> the output of ts_parse() in something simple such as '345' in a working
>> port with the failing one. That might give you clues as to what is
>> causing the failure.

> [ trace ]

As was suspected upthread, this shows that p_isdigit() is failing to
recognize "3" as a digit. So you've got broken locale support somewhere.

There are two different implementations of p_isdigit in wparser_def.c,
depending on whether USE_WIDE_UPPER_LOWER is defined. It should be, in
a Windows build, but maybe this is tracing back to a configure problem?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message marko 2014-01-26 23:02:21 BUG #8984: ERROR: t_xmin is uncommitted in tuple to be updated
Previous Message Marco Atzeri 2014-01-26 08:10:27 Re: BUG #8970: ts_parse incorrectly split numbers in digit token