[BUGS] BUG #5819: Translation Error of initdb's zh_CN.po
The following bug has been logged online: Bug reference: 5819 Logged by: yulei Email address: yu...@hotmail.com PostgreSQL version: 9.0.2 Operating system: Windows XP Service Pack 3 Description:Translation Error of initdb's zh_CN.po Details: Hi, I am a chinse , i found the src/bin/initdb/po/zh_CN.po have a translation error in line 608. there are five text search configuration strings in file zh_CN.po,four of them are translated by 文本搜索配置，but ,the one in line 608 is translated by 编码配置,that's wrong , it should like the other four. i suggest change: #: initdb.c:2881 #, c-format msgid %s: could not find suitable text search configuration for locale %s\n msgstr %s: 无法为语言环境\%s\ 找到合适的编码配置\n to #: initdb.c:2881 #, c-format msgid %s: could not find suitable text search configuration for locale %s\n msgstr %s: 无法为语言环境\%s\ 找到合适的文本搜索配置\n can you fixed it ？ -- 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 #5800: corrupted error messages (encoding problem ?)
On Tue, Dec 21, 2010 at 3:47 PM, Carlo Curatolo genam...@brutele.be wrote: The following bug has been logged online: Bug reference: 5800 Logged by: Carlo Curatolo Email address: genam...@brutele.be PostgreSQL version: 9.0.2 64bits Operating system: Windows 7 64bits Description: corrupted error messages (encoding problem ?) Details: On a new PC I install only Windows (French) and PosgreSQL 9.0.2 with default parameters and without creating any object. Example of corrupted error messages that occurs on several client software (my own Java program, dbVisualizer, EMS SQL Manager) [Error Code: 0, SQL State: 42601] ERREUR: erreur de syntaxe � la fin de l'entr�e Test 1 : Windows 7 64 bits and PosgreSQL 9.0.2 64 bits ... the problem occurs Test 2 : Windows 7 64 bits and PosgreSQL 9.0.2 32 bits ... the problem occurs Test 3 : Windows 7 32 bits and PosgreSQL 9.0.2 32 bits ... NO problem, the error message is correct [Error Code: 0, SQL State: 42601] ERREUR: erreur de syntaxe à la fin de l'entrée This issue occurs only when PostgreSQL 9.0.2 is installed on Windows 7 64 bits... FYI, we've been investigating this, however, whilst we can reproduce the same issue, we see it in different circumstances which conflict with yours: You reported: 64 bit OS, 64 bit PG - corruption 64 bit OS, 32 bit PG - corruption 32 bit OS, 32 bit PG - OK We see: 64 bit OS, 64 bit PG - OK 64 bit OS, 32 bit PG - corruption 32 bit OS, 32 bit PG - corruption That implies to us that this is something environmental, rather than a build or installer bug (between us, both installers work correctly on their native platforms). What does the environment look like on both of your servers? Try running \! set from a psql session in each. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- 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 #5800: corrupted error messages (encoding problem ?)
[Please keep messages on the mailing list] Hi, I don't see anything there that gives me any ideas. Anyone else have any ideas? 2011/1/7 Génération Amiga genam...@brutele.be: Hello Dave, Here are the result of \! set on the servers and I still have W7-32 and W7-64 (WinXP died) ** W7-64 and PG9-64 ** postgres=# \! set; =::=::\ =C:=C:\Program Files\PostgreSQL\9.0\scripts ALLUSERSPROFILE=C:\ProgramData APPDATA=C:\Users\Carlo\AppData\Roaming CLIENTENCODING_JP=0 CommonProgramFiles=C:\Program Files\Common Files CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files CommonProgramW6432=C:\Program Files\Common Files COMPUTERNAME=WIN7-64 ComSpec=C:\Windows\system32\cmd.exe database=postgres FP_NO_HOST_CHECK=NO HOMEDRIVE=C: HOMEPATH=\Users\Carlo LOCALAPPDATA=C:\Users\Carlo\AppData\Local LOGONSERVER=\\WIN7-64 NUMBER_OF_PROCESSORS=2 OS=Windows_NT Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\ PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC PGLOCALEDIR=C:/Program Files/PostgreSQL/9.0/share/locale PGSYSCONFDIR=C:/Program Files/PostgreSQL/9.0/etc port=5432 PROCESSOR_ARCHITECTURE=AMD64 PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 15 Stepping 6, GenuineIntel PROCESSOR_LEVEL=6 PROCESSOR_REVISION=0f06 ProgramData=C:\ProgramData ProgramFiles=C:\Program Files ProgramFiles(x86)=C:\Program Files (x86) ProgramW6432=C:\Program Files PROMPT=$P$G PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\ PUBLIC=C:\Users\Public server=localhost SESSIONNAME=Console SystemDrive=C: SystemRoot=C:\Windows TEMP=C:\Users\Carlo\AppData\Local\Temp TMP=C:\Users\Carlo\AppData\Local\Temp USERDOMAIN=WIN7-64 USERNAME=postgres USERPROFILE=C:\Users\Carlo windir=C:\Windows postgres=# ** W7-32 and PG9-32 ** postgres=# \! set; =::=::\ =C:=C:\Program Files\PostgreSQL\9.0\scripts ALLUSERSPROFILE=C:\ProgramData APPDATA=C:\Users\Carlo\AppData\Roaming CLIENTENCODING_JP=0 CommonProgramFiles=C:\Program Files\Common Files COMPUTERNAME=WIN7-32 ComSpec=C:\Windows\system32\cmd.exe database=postgres FP_NO_HOST_CHECK=NO HOMEDRIVE=C: HOMEPATH=\Users\Carlo LOCALAPPDATA=C:\Users\Carlo\AppData\Local LOGONSERVER=\\WIN7-32 NUMBER_OF_PROCESSORS=1 OS=Windows_NT Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\ PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC PGLOCALEDIR=C:/Program Files/PostgreSQL/9.0/share/locale PGSYSCONFDIR=C:/Program Files/PostgreSQL/9.0/etc port=5432 PROCESSOR_ARCHITECTURE=x86 PROCESSOR_IDENTIFIER=x86 Family 15 Model 2 Stepping 4, GenuineIntel PROCESSOR_LEVEL=15 PROCESSOR_REVISION=0204 ProgramData=C:\ProgramData ProgramFiles=C:\Program Files PROMPT=$P$G PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\ PUBLIC=C:\Users\Public server=localhost SESSIONNAME=Console SystemDrive=C: SystemRoot=C:\Windows TEMP=C:\Users\Carlo\AppData\Local\Temp TMP=C:\Users\Carlo\AppData\Local\Temp USERDOMAIN=Win7-32 USERNAME=postgres USERPROFILE=C:\Users\Carlo windir=C:\Windows postgres=# *** I can send you whatever you need, I don't touch anything to those servers. I use them only for testing and I have image backups. Best regards. Curatolo Carlo = = = = = = = = Message d'origine du 2011-01-07 à 11:41:30 = = = = = = = = On Tue, Dec 21, 2010 at 3:47 PM, Carlo Curatolo genam...@brutele.be wrote: The following bug has been logged online: Bug reference: 5800 Logged by: Carlo Curatolo Email address: genam...@brutele.be PostgreSQL version: 9.0.2 64bits Operating system: Windows 7 64bits Description: corrupted error messages (encoding problem ?) Details: On a new PC I install only Windows (French) and PosgreSQL 9.0.2 with default parameters and without creating any object. Example of corrupted error messages that occurs on several client software (my own Java program, dbVisualizer, EMS SQL Manager) [Error Code: 0, SQL State: 42601] ERREUR: erreur de syntaxe � la fin de l'entr�e Test 1 : Windows 7 64 bits and PosgreSQL 9.0.2 64 bits ... the problem occurs Test 2 : Windows 7 64 bits and PosgreSQL 9.0.2 32 bits ... the problem occurs Test 3 : Windows 7 32 bits and PosgreSQL 9.0.2 32 bits ... NO problem, the error message is correct [Error Code: 0, SQL State: 42601] ERREUR: erreur de syntaxe à la fin de l'entrée This issue occurs only when PostgreSQL 9.0.2 is installed on Windows 7 64 bits... FYI, we've been investigating this, however, whilst we can reproduce the same issue, we see it in different circumstances which conflict with yours: You reported: 64 bit OS, 64 bit PG - corruption 64 bit OS, 32 bit PG - corruption 32 bit OS, 32 bit PG - OK We see: 64 bit OS, 64 bit PG - OK 64 bit OS, 32 bit PG - corruption 32 bit OS, 32 bit PG - corruption
Re: [BUGS] BUG #5800: corrupted error messages (encoding problem ?)
On 07.01.2011 12:35, Dave Page wrote: [Please keep messages on the mailing list] Hi, I don't see anything there that gives me any ideas. Anyone else have any ideas? Hello, Yes. I would like to see output of CHCP. Which Windows codepage is used? 850? Susanne -- Susanne Ebrecht - 2ndQuadrant PostgreSQL Development, 24x7 Support, Training and Services www.2ndQuadrant.com -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] Re: to_timestamp returns the incorrect result for the DST fall over time.
Now this works great. Thanks for the help. Thanks, Gouse -- View this message in context: http://postgresql.1045698.n5.nabble.com/to-timestamp-returns-the-incorrect-result-for-the-DST-fall-over-time-tp3327393p3331798.html Sent from the PostgreSQL - bugs mailing list archive at Nabble.com. -- 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 #5800: corrupted error messages (encoding problem ?)
On Fri, Jan 7, 2011 at 12:37 PM, Susanne Ebrecht susa...@2ndquadrant.com wrote: On 07.01.2011 12:35, Dave Page wrote: [Please keep messages on the mailing list] Hi, I don't see anything there that gives me any ideas. Anyone else have any ideas? Hello, Yes. I would like to see output of CHCP. Which Windows codepage is used? 850? In our testing, the windows codepage was 1252, and the console codepage was 850 (giving the normal warning about the mismatch that we've seen for years). That was the case on installations with, and without the incorrect formatting. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- 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 #5820: FATAL: could not access file libpqwalreceiver: No such file or directory
The following bug has been logged online: Bug reference: 5820 Logged by: Leif Gunnar Erlandsen Email address: l...@lako.no PostgreSQL version: 9.0.2 Operating system: RedHat Enterprise 5.4 64 bit Description:FATAL: could not access file libpqwalreceiver: No such file or directory Details: Postgresql compiled from source and placed in /local/postgresql/9.0.2 libpqwalreceiver.so is located in /local/postgresql/9.0.2/lib64 while recovery is trying to load it from /local/postgresql/9.0.2/lib With symlink to libpqwalreceiver.so in lib problem disappears. Regards Leif Gunnar Erlandsen -- 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 #5819: Translation Error of initdb's zh_CN.po
Em 07-01-2011 03:52, yulei escreveu: Hi, I am a chinse , i found the src/bin/initdb/po/zh_CN.po have a translation error in line 608. Could you provide a new zh_CN.po with the corrected strings? Grab the PO file (initdb-zh_CN) from the 9.0 branch [1] and post it to Patch Tracker [2]. [1] http://babel.postgresql.org/ [2] http://pgfoundry.org/tracker/?group_id=164 -- Euler Taveira de Oliveira http://www.timbira.com/ -- 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 #5820: FATAL: could not access file libpqwalreceiver: No such file or directory
Leif Gunnar Erlandsen l...@lako.no writes: Postgresql compiled from source and placed in /local/postgresql/9.0.2 libpqwalreceiver.so is located in /local/postgresql/9.0.2/lib64 while recovery is trying to load it from /local/postgresql/9.0.2/lib .../lib is where I'd expect it to be. Did you move the libraries to .../lib64 by hand, or something like that? If so, you would need to modify the paths chosen by configure; you can't just manually rearrange the installation tree. 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
Re: [BUGS] BUG #5814: documentation bug
[moving to pgsql-docs] On Wed, Jan 5, 2011 at 8:04 AM, Antje Petersen antje.peter...@desy.de wrote: According to the documentation createuser --no-superuser and createuser --no-createrole is the default. This is not true. The default is to be asked Shall the new role be a superuser? (y/n) Shall the new role be allowed to create more new roles? (y/n) I agree that the incorrect claims about defaults for --superuser, --createrole, and --createdb should be gotten rid of, since there are no defaults for these options and createuser will force you to answer Y or N for these options if you didn't specify on the command line. Simple doc patch attached. I think the Examples section demonstrates that createuser will prompt for this information without having to belabor this point in the doc. Josh diff --git a/doc/src/sgml/ref/createuser.sgml b/doc/src/sgml/ref/createuser.sgml index 08c82e0..fbc184f 100644 --- a/doc/src/sgml/ref/createuser.sgml +++ b/doc/src/sgml/ref/createuser.sgml @@ -103,7 +103,6 @@ PostgreSQL documentation listitem para The new user will not be allowed to create databases. -This is the default. /para /listitem /varlistentry @@ -217,7 +216,6 @@ PostgreSQL documentation listitem para The new user will not be allowed to create new roles. -This is the default. /para /listitem /varlistentry @@ -238,7 +236,6 @@ PostgreSQL documentation listitem para The new user will not be a superuser. -This is the default. /para /listitem /varlistentry -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
