|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|Subject:||Re: BUG #15509: Pg_Dump failed if Database name contains non ascii characters|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
=?utf-8?q?PG_Bug_reporting_form?= <noreply(at)postgresql(dot)org> writes:
> 1) While installing postgres i have selected only Locale [Default Locale]
> and install postgres in win10
What would "Default Locale" mean?
> 2) Create a database with non ascii name example : Química Ltda
> Script used :-
> CREATE DATABASE "Química Ltda" WITH ENCODING='UTF8' OWNER postgres
> CONNECTION LIMIT=-1;
> 3) Use command prompt to take a pg_dump
> Command used
> --host localhost --port 7555 --username postgres --format=d --verbose
> --jobs=10 --compress 9 --file "C:\Delete\vt" --dbname "Química"
> 4) Error thrown
> pg_dump: [archiver (db)] connection to database "Química Ltda" failed:
> FATAL: database "Química Ltda" does not exist
The most likely theory here is that the encoding that was used to store
the name "Química Ltda" is not the same one that your terminal window
is using. Postgres doesn't provide any mechanism for transcoding database
or role names --- whatever bytes show up in the connection request packet
have to match what is in pg_database (resp. pg_authid). It'd be nice to
do better than that, but generally we have little idea at that point what
encoding the client thinks it's using.
Note that the command you show above doesn't guarantee that the database
name was stored with UTF8 encoding --- it would've been whatever encoding
was in use in the database you issued the CREATE DATABASE command in.
regards, tom lane
|Next Message||Michael Paquier||2018-11-16 08:32:52||Re: ALTER INDEX ... ALTER COLUMN not present in dump|
|Previous Message||PG Bug reporting form||2018-11-16 05:06:41||BUG #15509: Pg_Dump failed if Database name contains non ascii characters|