Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: tsearch in core patch
- From: Teodor Sigaev <teodor(at)sigaev(dot)ru>
- To: Hannu Krosing <hannu(at)skype(dot)net>
- Cc: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Subject: Re: tsearch in core patch
- Date: Fri, 22 Jun 2007 13:05:57 +0400
- Message-id: <467B90F5(dot)7000603(at)sigaev(dot)ru>
3) ALTER FULLTEXT CONFIGURATION cfgname ADD/ALTER/DROP MAPPING doneWhy not rename ALTER FULLTEXT CONFIGURATION --> ALTER TEXT SEARCH CONFIGURATION here too ?
It's renamed too.
most languages can be written using UNICODE charset and UTF-8 encoding, so neither charset not encoding can be used to determine language.
yes
--- how do many languages use ISO8859-1 locale?.
> ISO8859-1 is encoding, not locale.I meant, if we'll use encoding name (for example PG_LATIN1) we couldn't distinguish languages which use that encoding (for example italian and finnish and some more), but using locale names it's possible: it_IT.ISO8859-1, fi_FI.ISO8859-1
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
- Follow-Ups:
- Re: tsearch in core patch
- From: Alvaro Herrera
- Re: tsearch in core patch
- References:
- tsearch in core patch
- From: Teodor Sigaev
- Re: tsearch in core patch
- From: Hannu Krosing
- tsearch in core patch
- Prev by Date: Re: Worries about delayed-commit semantics
- Next by Date: Re: tsearch in core patch
- Previous by thread: Re: tsearch in core patch
- Next by thread: Re: tsearch in core patch
- Indexes: