BUG #13427: postgres.exe fails to start on Korean Windows Server 2008: cannot perform encoding conversion outsid

From: Dmitri(dot)Bourlatchkov(at)software(dot)dell(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #13427: postgres.exe fails to start on Korean Windows Server 2008: cannot perform encoding conversion outsid
Date: 2015-06-10 14:32:35
Message-ID: 20150610143235.2796.52303@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 13427
Logged by: Dmitri Bourlatchkov
Email address: Dmitri(dot)Bourlatchkov(at)software(dot)dell(dot)com
PostgreSQL version: 9.4.3
Operating system: Windows Server 2008 (Korean)
Description:

0. Log in as a local Administrator into a Korean version of the Windows
Server 2008
1. Install PostgreSQL 9.4.3 using the Windows .exe installer from
EnterpriseDB
2. Open cmd.exe shell
3. cd to potgresql/bin directory
4. Run postgresql.exe (no args)
5. Observe the following error message:

----
FATAL: XX000: cannot perform encoding conversion outside a transaction
LOCATION: pg_do_encoding_conversion, src\backend\utils\mb\mbutils.c:360
----

A similar message shows up when using pg_ctl.exe to start PostgreSQL.

Trouble-shooting attempted:
1. Run set LC_CTYPE=C
2. Run postgresql.exe (no args)
3. The following expected error shows up:

----
Execution of PostgreSQL by a user with administrative permissions is not
permitted.
The server must be started under an unprivileged user ID to prevent
possible system security compromises. See the documentation for
more information on how to properly start the server.
----

Note: PostgreSQL _is_ able to run as a Windows Service without any
environment modifications.

Note: If the LC_CTYPE=C env. variable is set, PosgreSQL can also be started
successfully via pg_ctl (under the Administrator user).

Thanks,

Dmitri.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message smoola 2015-06-10 16:19:19 BUG #13429: Update 0 rows for matching record
Previous Message jkoceniak 2015-06-10 14:02:24 BUG #13426: table bloat - dead rows not removed after vacuum