From: | Wilm Hoyer <W(dot)Hoyer(at)dental-vision(dot)de> |
---|---|
To: | Aetimpani Yeatina <aetimpani(at)yandex(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | AW: Stranger Character Input Bug |
Date: | 2020-06-24 07:00:07 |
Message-ID: | 54f6dca53f0d43ebb4c14c1ce77ce37a@dental-vision.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
> Hi. I suppose found a bug. I have explained that on stackoverflow (Link: https://stackoverflow.com/questions/62535206/postgresql-doesnt-respond-when-i-input-stranger-character-on-cmd )
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 https://www.postgresql.org/docs/current/sql-syntax-lexical.html
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.
Regards
Wilm.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2020-06-24 07:59:21 | Re: BUG #16476: pgp_sym_encrypt_bytea with compress-level=6 : Wrong key or corrupt data |
Previous Message | Hardik Bansal | 2020-06-23 23:06:36 | Very slow inserts when using postgres_fdw + declarative partitioning |