RaphaÃl Enrici wrote:
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.
Might be because of Unicode, or an additional backend side problem.
Anyhow, this must be examined on pgsql-hackers. We cert
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-bu
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
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 fi
Ricardo just sent me an email where saying the problem also appears in psql:
a) leave lc_messages = '[EMAIL PROTECTED]'; export [EMAIL PROTECTED] ;
/etc/init.d/postgresql restart
:~ > psql xxx
Contraseña:
Bienvenido a psql 7.4.3, el terminal interactivo de PostgreSQL.
Digite: \copyright para ver
Hi Andreas,
hope I won't mess you with a known one...
Andreas Pflug wrote:
Raphaël Enrici wrote:
can one of you confirm that error messages displayed under the SQL
query window are generated by the PostgreSQL backend and not by
pgAdmin III ?
That's correct, everything in the message tab and in c
