Skip site navigation (1) Skip section navigation (2)

Re(2): 7.0.3 -> 7.1.2; pg_setlocale error

From: "pgsql-admin" <pgsql-admin(at)fc(dot)emc(dot)com(dot)ph>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re(2): 7.0.3 -> 7.1.2; pg_setlocale error
Date: 2001-06-20 13:18:29
Message-ID: fc.000f567200c5e060000f567200c5e060.c5e0f5@fc.emc.com.ph (view raw or flat)
Thread:
Lists: pgsql-admin
zakkr(at)zf(dot)jcu(dot)cz writes:
>On Thu, Jun 14, 2001 at 11:34:06PM +0800, pgsql-admin wrote:
>
>> NOTICE:  copy: line 1, pg_setlocale(): 'LC_COLLATE=??' cannot be
>honored.
>> NOTICE:  copy: line 1, pg_setlocale(): 'LC_CTYPE=¡T0(at)X' cannot be
>honored.
>> NOTICE:  copy: line 1, pg_setlocale(): 'LC_MONETARY=X?' cannot be
>honored.
>
> This message is reported if standard setlocale(3) returns error. IMHO 
>isn't PG problem, but something is bad in your system or PG setting. 
> 
> But why the copy call pg_setlocale() .. any trigger or function in
>domain 
>integrity checking/setting in the table definition?
>
>						Karel

according to the logs pg_dump was performing 'copy from stdin' and the
data has money data type.

I am wrong in my last email saying that it only affects one of our table
that
has money data type. I just saw the same error in the regression test.
What gives?

Sherwin


FROM "regression.diffs" 

<CUT>

*** ./expected/int8.out Sat Jan 27 06:50:26 2001
--- ./results/int8.out  Wed Jun 20 19:51:40 2001
***************
*** 111,116 ****
--- 111,119 ----
  --
  SELECT '' AS to_char_1, to_char(q1, '9G999G999G999G999G999'),
to_char(q2, '9,999,999,999,999,999')
        FROM INT8_TBL;
+ NOTICE:  pg_setlocale(): 'LC_COLLATE=~HÆ^]^H(at)Ç^]^H^P' cannot be honored.
+ NOTICE:  pg_setlocale(): 'LC_CTYPE=°t!(at)^XÕ^]^H^P' cannot be honored.
+ NOTICE:  pg_setlocale(): 'LC_MONETARY=^XÕ^]^HhN&^H^P' cannot be honored.
   to_char_1 |        to_char         |        to_char
  -----------+------------------------+------------------------
             |                    123 |                    456

<CUT>

*** ./expected/numeric.out      Sat Apr  8 03:17:42 2000
--- ./results/numeric.out       Wed Jun 20 19:51:50 2001
***************
*** 698,703 ****
--- 698,706 ----
  --
  SELECT '' AS to_char_1, to_char(val, '9G999G999G999G999G999')
        FROM num_data;
+ NOTICE:  pg_setlocale(): 'LC_COLLATE=~HÆ^]^H(at)Ç^]^H^P' cannot be honored.
+ NOTICE:  pg_setlocale(): 'LC_CTYPE=°t!(at)^XÕ^]^H^P' cannot be honored.
+ NOTICE:  pg_setlocale(): 'LC_MONETARY=^XÕ^]^H| ²#^H^P' cannot be honored.
   to_char_1 |        to_char
  -----------+------------------------
             |                     0

<CUT>

*** ./expected/rules.out        Wed Dec  6 03:15:48 2000
--- ./results/rules.out Wed Jun 20 19:52:24 2001
***************
*** 52,57 ****
--- 52,60 ----
  create rule rtest_emp_ins as on insert to rtest_emp do
        insert into rtest_emplog values (new.ename, current_user,
                        'hired', new.salary, '0.00');
+ NOTICE:  pg_setlocale(): 'LC_COLLATE=~HÆ^]^H(at)Ç^]^H^P' cannot be honored.
+ NOTICE:  pg_setlocale(): 'LC_CTYPE=°t!(at)^XÕ^]^H^P' cannot be honored.
+ NOTICE:  pg_setlocale(): 'LC_MONETARY=^XÕ^]^H¨P&^H^P' cannot be honored.
  create rule rtest_emp_upd as on update to rtest_emp where new.salary !=
old.salary do
        insert into rtest_emplog values (new.ename, current_user,
                        'honored', new.salary, old.salary);


pgsql-admin by date

Next:From: Shaun ThomasDate: 2001-06-20 13:18:48
Subject: Notice logging.
Previous:From: Christof GlaserDate: 2001-06-20 11:03:49
Subject: Re: Row Level Locking !!

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group