| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | John DeSoi <desoi(at)pgedit(dot)com>, Postgresql General List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: changing text search treatment of puncutation |
| Date: | 2008-07-03 07:28:53 |
| Message-ID: | 486C7FB5.7050704@sigaev.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> In general there seem to be a lot of ways that people wish they
> could tweak the text search parser, and telling them to write
> their own parser isn't a very helpful response for most folk.
> I don't have an idea about how to improve the situation, but
> it seems like something that should be thought about.
We (with Oleg) thought hard about it and we don't find a solution yet.
Configurable parser should be:
- fast
- flexible
- not error-prone
- comfortable to use by non-programmer (at least for non-C programmer)
It might be a table-driven state machine (just put TParserStateAction into
table(s) with some caching for first step) , but it's complex to operate and
it's needed to prove correctness of changes in states before its become in use.
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2008-07-03 07:42:10 | Re: pg_dump - lost synchronization with server: got message type "d", length 6036499 |
| Previous Message | Dave Coventry | 2008-07-03 06:42:56 | Re: SAST FATAL: could not access private key file "server.key" |