| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jadhav, Manadeep (BHGE)" <Manadeep(dot)Jadhav(at)bhge(dot)com> |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>, "Periyaswamy, Balakrishnan (BHGE, Non-GE)" <balakrishnan(dot)periyaswamy(at)bhge(dot)com>, "Sabale, Sachin (BHGE)" <Sachin(dot)Sabale(at)bhge(dot)com>, "Kapoor, Chandan I (BHGE)" <chandan(dot)kapoor(at)bhge(dot)com> |
| Subject: | Re: Issue while non-english character in userid and password |
| Date: | 2019-01-17 15:19:32 |
| Message-ID: | 13121.1547738372@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Jadhav, Manadeep (BHGE)" <Manadeep(dot)Jadhav(at)bhge(dot)com> writes:
> We are using postgres server install on windows 7 32 bit machine in Spanish and for database username and password we have used non-English character í, with this userid and password we are able to connect the database but when we try to run the backup for same db using pg_dump utility it fails saying error as "password authentication failed". Please let us know how can we handle this issue.
If you use characters outside the base ASCII set in user or database names
or passwords, it's up to you to ensure that those characters are always
sent the same way in connection requests. Postgres can't do any encoding
conversion on connection requests since it doesn't know what character set
the client is using. Presumably what's happening here is that the backup
script isn't running with the same code page you used when creating the
password.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | bharath Ganesan | 2019-01-17 17:20:36 | Re: Installation issue |
| Previous Message | Sandeep Thakkar | 2019-01-17 15:11:18 | Re: Installation issue |