[BUGS] BUG #6308: Problem w. encoding in client
The following bug has been logged online: Bug reference: 6308 Logged by: Thomas Goerner Email address: t...@clickware.de PostgreSQL version: 9.1.1 Operating system: Windows 7 64-bit Description:Problem w. encoding in client Details: Hi, we have a problem regarding encoding with postgres 9.1.1 and Win7 64-bit Database encoding: UTF-8 active codepage in Windows console: 1252 PGCLIENTENCODING: Win1252 Console font: Lucida console In the above configuration, the following problems occur: 1) Text output from the client applications, e.g. the welcome-prompt of psql or the help page from pg_dump --help is not displayed correctly (especially german Umlauts and characters like "«" ). 2) When we restore a dump in custom format and then try to re-dump the database, we get error messages like Zeichen 0xe28093 in Kodierung »UTF8« hat keine Entsprechung in »Win1252« (character 0xe28093 in UTF-8 cannot be translated to Win1252) The above configuration is our standard configuration and works just fine in Windows XP and even in Windows 7 32-bit. Is there any solution to this problem? Thanks in advance Thomas -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] BUG #6309: ECPG pre-processor issue
The following bug has been logged online:
Bug reference: 6309
Logged by: Andrew Milne
Email address: andrew.mi...@iongeo.com
PostgreSQL version: 8.4.9
Operating system: Red Hat Enterprise Linux Workstation release 6.1
(Santiago)
Description:ECPG pre-processor issue
Details:
NOTE: While I've not tested on 9.1 I can see the same code exists in that
release and as such the error will most likely still occur. Unfortunately I
can't upgrade from 8.4.9 due to project wide considerations.
The ECPG pre-processor seems to be incorrectly reporting an error when
parsing "EXEC SQL AT :cnx DEALLOCATE..." style commands.
For example:
===
EXEC SQL AT :cnx DEALLOCATE thestatementname;
===
results in the pre-processor outputting an error:
===
src.pcpp:1000: ERROR: AT option not allowed in DEALLOCATE statement
===
However if you examine the generated src.cpp file it appears to have
correctly generated code that uses the connection:
===
{ ECPGdeallocate(__LINE__, 0, cnx, "thestatementname");
===
And examining the source code for ECPGdeallocate it correctly handles the
supplied connection.
Examining the pre-processor (preproc.y) seems to show this error has no
impact on the actual processing of the file and is probably just a holdover
from earlier versions of ECPG.
The project I'm working on has multiple ECPG connections open and we need to
be able to prepare and deallocate to the correct connection. Our intention
is to simply ignore the preprocessor error at this time but it would be good
to:
1. Get some confirmation that this is safe to do
2. If someone with a decent knowledge of postgress could actually look into
fixing the issue it would be appreciated (my understanding is limited and I
wouldn't be confident putting forward a patch myself).
Thanks
A Milne
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] BUG #6310: Startup Script
The following bug has been logged online:
Bug reference: 6310
Logged by: Sidar Lopez
Email address: sidar.lo...@gmail.com
PostgreSQL version: 9.1.1
Operating system: Mac OS X
Description:Startup Script
Details:
Log file is not being created at ${PGLOG} location.
Change this line at Mac OS X startup script in StartService ():
sudo -u $PGUSER sh -c "${DAEMON} -D '${PGDATA}' &" 2>&1 | ${LOGUTIL}
'${PGLOG}' ${ROTATESEC} &
by this one:
sudo -u $PGUSER sh -c "${DAEMON} -D '${PGDATA}' &" 2>&1 | ${LOGUTIL}
${PGLOG} ${ROTATESEC} &
and this one in RestartService ():
sudo -u $PGUSER sh -c "${DAEMON} -D '${PGDATA}' &" 2>&1 | ${LOGUTIL}
'${PGLOG}' ${ROTATESEC} &
by this one:
sudo -u $PGUSER sh -c "${DAEMON} -D '${PGDATA}' &" 2>&1 | ${LOGUTIL}
${PGLOG} ${ROTATESEC} &
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6310: Startup Script
"Sidar Lopez" writes:
> Operating system: Mac OS X
> Description:Startup Script
> Log file is not being created at ${PGLOG} location.
Hmm, yeah, that's overly-quoted. Will fix, thanks for the report!
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
