[BUGS] BUG #2181: Bug in SQLNumResultCols
The following bug has been logged online: Bug reference: 2181 Logged by: Thomas Goerner Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1 Operating system: WinXP Description:Bug in SQLNumResultCols Details: calling SQLNumResultCols on a hstmt that has been executed previously and then closed using SQLFreeStmt(m_hstmt, SQL_CLOSE) (MFC's CRecordset::Requery() does this) re-executes the statement. ODBC driver version is 8.01.01.02. ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[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
Re: [BUGS] BUG #6308: Problem w. encoding in client
Hello Craig, thanks for your answer. > Restore using PgAdmin III or using a unicode console. > This is a limitation of using a Win1252 client encoding when restoring > data that isn't restricted to Win1252 and cannot be fixed directly. That's new to me. AFAIK pg_restore looks into the dump file and sets the client encoding accordingly (In fact the dump contains the statement SET client_encoding = 'UTF8';). Is this overridden by PGCLIENTENCODING? And if so, should it be? And as we only encounter both problems in Windows7-64, it seems to me they are closely related. Regards Thomas === click:ware Informationstechnik GmbH Thomas Goerner Geschäftsführer fon: 0221 - 13 99 88-0 fax: 0221 - 13 99 88-79 Kamekestraße 19 50672 Köln t...@clickware.de www.clickware.de === Kennen Sie schon unser GasDataWarehouse - Die kostengünstige Lösung für den Austausch von Gasmessdaten? www.gasdatawarehouse.de -Ursprüngliche Nachricht- Von: Craig Ringer [mailto:ring...@ringerc.id.au] Gesendet: Sonntag, 27. November 2011 10:00 An: Thomas Goerner Cc: pgsql-bugs@postgresql.org Betreff: Re: [BUGS] BUG #6308: Problem w. encoding in client On 11/25/2011 08:21 PM, Thomas Goerner wrote: > > 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 "«" ). That shouldn't be happening. As a workaround, try using a unicode console (see the "chcp" command) and a unicode client encoding. The issue with mismatched chars sounds like a real bug that wants looking into. > 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) Restore using PgAdmin III or using a unicode console. This is a limitation of using a Win1252 client encoding when restoring data that isn't restricted to Win1252 and cannot be fixed directly. If you don't mind possibly corrupted error and NOTICE messages you can just set a unicode client_encoding for your restore. -- Craig Ringer
Re: [BUGS] BUG #6308: Problem w. encoding in client
Hello Craig, it seems as if there were illegal chars in the originally dumped database, so the dump/restore problem might be due to this. At the moment we are doing further investigation on this issue. But the problem regarding message output from the client applications still persists. We are now setting up another set of 32/64-bit (virtual) Windows 7 machines to verify that the problem occurs only on 64 bit windows. I will keep you informed. Regards Thomas === click:ware Informationstechnik GmbH Thomas Goerner Geschäftsführer fon: 0221 - 13 99 88-0 fax: 0221 - 13 99 88-79 Kamekestraße 19 50672 Köln <mailto:t...@clickware.de> t...@clickware.de <http://www.clickware.de/> www.clickware.de === Kennen Sie schon unser GasDataWarehouse - Die kostengünstige Lösung für den Austausch von Gasmessdaten? <http://www.gasdatawarehouse.de/> www.gasdatawarehouse.de _ Von: Craig Ringer [mailto:ring...@ringerc.id.au] Gesendet: Dienstag, 29. November 2011 03:33 An: Thomas Goerner Cc: pgsql-bugs@postgresql.org Betreff: Re: [BUGS] BUG #6308: Problem w. encoding in client On 11/28/2011 08:26 PM, Thomas Goerner wrote: Hello Craig, thanks for your answer. > Restore using PgAdmin III or using a unicode console. > This is a limitation of using a Win1252 client encoding when restoring > data that isn't restricted to Win1252 and cannot be fixed directly. That's new to me. AFAIK pg_restore looks into the dump file and sets the client encoding accordingly (In fact the dump contains the statement SET client_encoding = 'UTF8';). Is this overridden by PGCLIENTENCODING? And if so, should it be? Nope, pg_restore should be using UTF8 as the client encoding in that case. If there are any errors or notices it won't be able to emit them correctly on the terminal though, as win1252 can't represent everything in UTF8 (and IIRC pg_restore doesn't recode from client_encoding to terminal encoding anyway). If the restore its self is failing then I agree that something's not working properly, because you should be able to use a client_encoding different to your terminal encoding. I wonder if recent changes intended to get psql to pick up the terminal encoding automatically have had the unintended side-effect of overriding pg_restore's attempt to set the client_encoding? I'm rather surprised you only see this on x64. You're using the same Windows and Pg version for both x64 and x64 but only the x64 test fails? -- Craig Ringer
