Skip site navigation (1) Skip section navigation (2)

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

From: Alexander Law <exclusion(at)gmail(dot)com>
To: Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #6742: pg_dump doesn't convert encoding of DB object names to OS encoding
Date: 2012-07-18 08:51:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugspgsql-generalpgsql-hackers

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 dump encoding and thus 
they're getting unreadable when different encoding is used.
The same can be reproduced in Linux (where console encoding is UTF-8) 
when doing dump with Windows-1251 or Latin1 (for western european 


    The following bug has been logged on the website:

    Bug reference:      6742
    Logged by:          Alexander LAW
    Email address:      exclusion(at)gmail(dot)com
    PostgreSQL version: 9.1.4
    Operating system:   Windows

    When I try to dump database with UTF-8 encoding in Windows, I get unreadable
    object names.
    Please look at the screenshot ( On the
    left window all the pg_dump messages displayed correctly (except for the
    prompt password (bug #6510)), but the non-ASCII object name is gibberish. On
    the right window (where dump is done with the Windows 1251 encoding (OS
    Encoding for Russian locale)) everything is right.

Did you check the dump file using an editor that can handle UTF-8?
The Windows console is not known for properly handling that encoding.


In response to


pgsql-hackers by date

Next:From: Marko KreenDate: 2012-07-18 10:13:17
Subject: [9.1] 2 bugs with extensions
Previous:From: Heikki LinnakangasDate: 2012-07-18 07:30:40
Subject: Re: Checkpointer split has broken things dramatically (was Re: DELETE vs TRUNCATE explanation)

pgsql-bugs by date

Next:From: spatarel1Date: 2012-07-18 12:39:30
Subject: BUG #6743: BETWEEN operator does not work for char(1)
Previous:From: Thomas KellererDate: 2012-07-18 07:21:53
Subject: Re: BUG #6742: pg_dump doesn't convert encoding of DB object names to OS encoding

pgsql-general by date

Next:From: Radosław SmoguraDate: 2012-07-18 09:00:25
Subject: Re: Can't reset password
Previous:From: KOTaDate: 2012-07-18 08:33:10
Subject: Re: installation problem with postgres password

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group