> Hi. I suppose found a bug. I have explained that on stackoverflow (Link:
I think, this is a limitation oft he windows command shell, not a PostgreSQL bug (i’m not a PostgreSQL developer, so i might be wrong on that point)
You might give any of the following workarounds a try:
- Microsoft is currently working on „Windows Terminal“ with full UTF-8 character support – you can download a beta of that software from Microsoft Store.
- Use a third Party Command Line Tool
- Use the PostgreSQL Unicode Escape Syntax for literals for your input values – see
e.g. insert into jobs(id, name) values (10, E'a\uxxxxs\uxxxx') – you have to replace the xxxx with the unicode codepoint value of the character
- Use the „Linux on Windows Subsystem“ Windows 10 feature – inside the Linux distribution you choose as your subsystem, you can use a shell with full unicode character set support for your commands
As a side note: IIRC the windows power shell suffers from the same limitations as the command line tool, so using that toll as workaround will not help with your problem.