Re: fulltext parser strange behave

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
Subject: Re: fulltext parser strange behave
Date: 2007-11-07 23:38:33
Message-ID: 47324C79.3090400@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:
> "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> writes:
>
>> I am writing tsearch2 wrapper and I testing functionality. I found
>> some little bit strange on default parser. It can't parse tags with
>> numbers:
>>
>
> Well, the state machine definitely thinks that tag names should contain
> only ASCII letters (with possibly a leading or trailing '/'). Given the
> HTML examples I suppose we should allow non-first digits too. Is there
> anything else that should be considered a tag? What about dash and
> underscore for instance?
>
>
>

The docs say we specifically accept HTML tags. Are we really just
accepting anything that is a string of ASCII letters as the tag name?
Then we should adjust the docs. <foo> and <foo1234> are not HTML tags.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message CaT 2007-11-07 23:41:56 Re: Feature Request: inline comments
Previous Message Guillaume Smet 2007-11-07 23:36:16 Re: Estimation problem with a LIKE clause containing a /

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2007-11-08 01:11:37 Re: fulltext parser strange behave
Previous Message Tom Lane 2007-11-07 23:11:00 Re: fulltext parser strange behave