Raphaël Enrici wrote:
> Andreas Pflug wrote:
>
>> Raphaël Enrici wrote:
>>
>>> Ricardo just sent me an email where saying the problem also appears
>>> in psql:
>>>
>>>
>>> xxx=# select * from non_existent;
>>> ERROR: ERRORDATA_STACK_SIZE exceeded
>>> xxx=#
>>
>>
>> So that's obviously a backend problem, and this stuff should go to
>> pgsql-bugs. Maybe a corrupted es_ES translation file.
>
>
> Thank you Andreas, we have found a workaround with Ricardo so that he
> can use his db correctly. We will move to the correct lists or Debian
> bug system to report this one.
Sorry to insist, but I'd like to come back on this...
To get the ERRORDATA_STACK_SIZE in psql it's mandatory to do one more
thing than in pgAdmin III.
I mean pgAdmin gets in error in situation where psql does not... Maybe
there is something else hidden far far far [(c) schrek2 ;)] ?
Here is where I am:
As root:
put lc_messages to es_ES in postgresql.conf
export LC_CTYPE=es_ES # LC_CTYPE, not LC_MESSAGES, or fr_FR, or
something not C, not POSIX, not xxx.UTF-8
/etc/init.d/postgresql restart
then in another terminal with locales set to POSIX as a normal user:
ralph@anacond:~$ pgadmin3 => DOES NOT WORK CORRECTLY
ralph@anaconda:~$ psql -d pipo2
Welcome to psql 7.4.3, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help on internal slash commands
\g or terminate with semicolon to execute query
\q to quit
pipo2=# \encoding
UNICODE
pipo2=# select * from doesnotexist;
ERROR: no existe la relaci�n "doesnotexist" ========> SO IT WORKS!
pipo2=# \encoding LATIN9 # IS IT REALLY MEANINGFUL TO DO SUCH A THING ???
pipo2=# select * from doesnotexist;
ERROR: ERRORDATA_STACK_SIZE exceeded ========> NOW IT DOES NOT WORK.
pipo2=#
So, I have to change my encoding to LATIN9 so that psql does not work
when pgadmin3 does not work at all.
As far as I've seen in pgadmin.log, the encoding selected by pga3 is
UNICODE as expected...
Any idea ? Is it worth investigating more ?
Regards,
Raphaël