Thread: Tsearch2 default locale on postgres 8.2

Tsearch2 default locale on postgres 8.2

From
"Tarabas (Manuel Rorarius)"
Date:
Hi!

   I am having a tsearch2 problem on postgres 8.2 again ...
   when I try to set the default config for tsearch2 with

   "select set_curcfg('default'); it works fine in the same pgadmin
   session when i use "select show_curcfg();" afterwards. The correct
   OID is shown.

   If i then close the query window and open a new one and then try
   the "select show_curcfg();" again, it states
   "ERROR:  could not find tsearch config by locale"

   Any idea why the configuration is not saved correctly?

Best regards
Manuel ...


Re: Tsearch2 default locale on postgres 8.2

From
Teodor Sigaev
Date:
set_curcfg() is working only for current session

Tarabas (Manuel Rorarius) wrote:
> Hi!
>
>    I am having a tsearch2 problem on postgres 8.2 again ...
>    when I try to set the default config for tsearch2 with
>
>    "select set_curcfg('default'); it works fine in the same pgadmin
>    session when i use "select show_curcfg();" afterwards. The correct
>    OID is shown.
>
>    If i then close the query window and open a new one and then try
>    the "select show_curcfg();" again, it states
>    "ERROR:  could not find tsearch config by locale"
>
>    Any idea why the configuration is not saved correctly?
>
> Best regards
> Manuel ...
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster

--
Teodor Sigaev                                   E-mail: teodor@sigaev.ru
                                                    WWW: http://www.sigaev.ru/

Re: Tsearch2 default locale on postgres 8.2

From
Hannes Dorbath
Date:
I think the best way is to adjust the locale for your default config:

Type:
SHOW lc_ctype; (or some other lc_* variables) in psql.

to find your cluster locale, then:

UPDATE
   public.pg_ts_cfg
SET
   locale = '<your_locale>'
WHERE
   ts_name = 'default';


On 22.12.2006 11:55, Tarabas (Manuel Rorarius) wrote:
>    I am having a tsearch2 problem on postgres 8.2 again ...
>    when I try to set the default config for tsearch2 with
>
>    "select set_curcfg('default'); it works fine in the same pgadmin
>    session when i use "select show_curcfg();" afterwards. The correct
>    OID is shown.
>
>    If i then close the query window and open a new one and then try
>    the "select show_curcfg();" again, it states
>    "ERROR:  could not find tsearch config by locale"
>
>    Any idea why the configuration is not saved correctly?

--
Regards,
Hannes Dorbath

Re: Tsearch2 default locale on postgres 8.2

From
"Tarabas (Manuel Rorarius)"
Date:
Hi,

right ... i had a typo in the locale, it was set to "de_DE.UTF8" but
should have been set to "de_DE.UTF-8".

After that change, the "select set_curcfg('default');" worked fine.

thanx a lot...

Best regards
Manuel

Friday, December 22, 2006, 12:35:41 PM, you wrote:

HD> I think the best way is to adjust the locale for your default config:

HD> Type:
HD> SHOW lc_ctype; (or some other lc_* variables) in psql.

HD> to find your cluster locale, then:

HD> UPDATE
HD>    public.pg_ts_cfg
HD> SET
HD>    locale = '<your_locale>'
HD> WHERE
HD>    ts_name = 'default';


HD> On 22.12.2006 11:55, Tarabas (Manuel Rorarius) wrote:
>>    I am having a tsearch2 problem on postgres 8.2 again ...
>>    when I try to set the default config for tsearch2 with
>>
>>    "select set_curcfg('default'); it works fine in the same pgadmin
>>    session when i use "select show_curcfg();" afterwards. The correct
>>    OID is shown.
>>
>>    If i then close the query window and open a new one and then try
>>    the "select show_curcfg();" again, it states
>>    "ERROR:  could not find tsearch config by locale"
>>
>>    Any idea why the configuration is not saved correctly?



Re: Tsearch2 default locale on postgres 8.2

From
Hannes Dorbath
Date:
I don't think calling set_curcfg() is necessary for anything in that
case then..

On 22.12.2006 12:36, Tarabas (Manuel Rorarius) wrote:
> After that change, the "select set_curcfg('default');" worked fine.


--
Regards,
Hannes Dorbath