Re: bug report: initdb failure on Microsoft Windows if path to initdb contains special chars - Mailing list pgsql-bugs

From Tom Lane
Subject Re: bug report: initdb failure on Microsoft Windows if path to initdb contains special chars
Date
Msg-id 642665.1738684548@sss.pgh.pa.us
Whole thread Raw
List pgsql-bugs
=?utf-8?B?U3TDtmNrZXIgQmVybmhhcmQgLSBha3RpdndlYiBHbWJI?= <bernhard.stoecker@aktivweb.de> writes:
> I’d like to report an issue concerning initdb on Microsoft Windows if running initdb.exe from a directory that
containsspecial chars like German umlauts. The error message is: FATAL: invalid byte sequence for encoding "UTF8": 0xf6
0x630x6b 

The directory name contains those, you mean?

Our position on this is that the data directory's path name has to be
valid in the encoding you are selecting for the database.  Otherwise
it's just too much of a mess to deal with inside-the-database values
like the data_directory setting.  It looks like you are using some
single-byte encoding (probably a Windows code page?) for your
filesystem names, so you should do the same for initdb's -E option.
Or switch to an all-ASCII path name.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #18793: PLpgSQL Function Returning Type of Table is not match for varchar(n) data type via Return Query
Next
From: PG Bug reporting form
Date:
Subject: BUG #18795: Norwegian bokmål crashes again