[BUGS] BUG #6742: pg_dump doesn't convert encoding of DB object names to OS encoding

2012-07-18 Thread exclusion
The following bug has been logged on the website: Bug reference: 6742 Logged by: Alexander LAW Email address: exclus...@gmail.com PostgreSQL version: 9.1.4 Operating system: Windows Description: When I try to dump database with UTF-8 encoding in Windows, I get unreada

[BUGS] Re: BUG #6742: pg_dump doesn't convert encoding of DB object names to OS encoding

2012-07-18 Thread Thomas Kellerer
exclus...@gmail.com, 18.07.2012 09:17: The following bug has been logged on the website: Bug reference: 6742 Logged by: Alexander LAW Email address: exclus...@gmail.com PostgreSQL version: 9.1.4 Operating system: Windows Description: When I try to dump database with UTF-8 e

[BUGS] Re: BUG #6742: pg_dump doesn't convert encoding of DB object names to OS encoding

2012-07-18 Thread Alexander Law
Hello, The dump file itself is correct. The issue is only with the non-ASCII object names in pg_dump messages. The messages text (which is non-ASCII too) displayed consistently with right encoding (i.e. with OS encoding thanks to libintl/gettext), but encoding of db object names depends on the

Re: [BUGS] main log encoding problem

2012-07-18 Thread Alexander Law
Hello! May I to propose a solution and to step up? I've read a discussion of the bug #5800 and here is my 2 cents. To make things clear let me give an example. I am a PostgreSQL hosting provider and I let my customers to create any databases they wish. I have clients all over the world (so they

Re: [BUGS] BUG #6733: All Tables Empty After pg_upgrade (PG 9.2.0 beta 2)

2012-07-18 Thread Mike Wilson
Tom, after patching pg_upgrade now runs successfully. I noticed that this patch had been applied since yesterday to the REL9_2_STABLE so I also tested with a git pull without the patch that appears to work also. I think issue has been resolved for me, thanks so much! You guys rock! Mike Wils

Re: [BUGS] main log encoding problem

2012-07-18 Thread Tatsuo Ishii
> C. We have one logfile with UTF-8. > Pros: Log messages of all our clients can fit in it. We can use any > generic editor/viewer to open it. > Nothing changes for Linux (and other OSes with UTF-8 encoding). > Cons: All the strings written to log file should go through some > conversation function

Re: [BUGS] main log encoding problem

2012-07-18 Thread Tom Lane
Tatsuo Ishii writes: > My idea is using mule-internal encoding for the log file instead of > UTF-8. There are several advantages: > 1) Converion to mule-internal encoding is cheap because no conversion >table is required. Also no information loss happens in this >conversion. > 2) Mule-in

Re: [BUGS] main log encoding problem

2012-07-18 Thread Tatsuo Ishii
> Tatsuo Ishii writes: >> My idea is using mule-internal encoding for the log file instead of >> UTF-8. There are several advantages: > >> 1) Converion to mule-internal encoding is cheap because no conversion >>table is required. Also no information loss happens in this >>conversion. > >

Re: [BUGS] main log encoding problem

2012-07-18 Thread Craig Ringer
On 07/18/2012 11:16 PM, Alexander Law wrote: Hello! May I to propose a solution and to step up? I've read a discussion of the bug #5800 and here is my 2 cents. To make things clear let me give an example. I am a PostgreSQL hosting provider and I let my customers to create any databases they wi

[BUGS] BUG #6743: BETWEEN operator does not work for char(1)

2012-07-18 Thread spatarel1
The following bug has been logged on the website: Bug reference: 6743 Logged by: Spătărel Dan Email address: spatar...@yahoo.com PostgreSQL version: 9.1.4 Operating system: Windows Vista SP2 Description: I use "UTF8" charset and "Romania, Romanian" locale. I came acr

Re: [BUGS] main log encoding problem

2012-07-18 Thread Alexander Law
Hello, C. We have one logfile with UTF-8. Pros: Log messages of all our clients can fit in it. We can use any generic editor/viewer to open it. Nothing changes for Linux (and other OSes with UTF-8 encoding). Cons: All the strings written to log file should go through some conversation function.