Re: Authentication failed when Password contains Japaneese Charecters

Try change the encoding of sesssions at database nivel to UTF8; this
encoding is taked as default for sessions
http://www.postgresql.org/docs/8.1/static/sql-alterdatabase.html ; try
ALTER DATABASE databasename SET ENCODING TO 'UTF8'
(or maybe UFT8 directly).
or if this don't work try
ALTER DATABASE databasename SET client_encoding TO 'UTF8'
or.... from Java set the econding of connections on creation or
configuration time (I don't know where exactly, but sure it's possible).

Shivender Devarakonda escribió:
>
> When I did the psql -l I see the following DBs in my local environment:
>
> C:\PostgreSQL\bin>psql -l
>         List of databases
>    Name    |  Owner   | Encoding
> -----------+----------+-----------
>  cmdb     | admin    | UTF8
>  postgres  | postgres | SQL_ASCII
>  template0 | postgres | SQL_ASCII
>  template1 | postgres | SQL_ASCII
>
> I am using cmdb which is UTF8.
>
> I think it is consistent with my application? any thoughts what might
> be wrong.
>
> Thanks,
> Shivender
> On Tue, Apr 20, 2010 at 7:07 PM, Shivender Devarakonda
> <shivenderd@gmail.com <mailto:shivenderd@gmail.com>> wrote:
>
>     Thanks. Where should I look for this property?
>
>     Thanks,
>     Shivender
>
>
>
>
>     On Tue, Apr 20, 2010 at 6:18 PM, Tom Lane <tgl@sss.pgh.pa.us
>     <mailto:tgl@sss.pgh.pa.us>> wrote:
>
>         Shivender Devarakonda <shivenderd@gmail.com
>         <mailto:shivenderd@gmail.com>> writes:
>         > I did not give any explicit encoding while creating the DB.
>         I am running
>         > postgres on Windows XP system.
>
>         Well, you should look at what server_encoding is set to, then.
>         If it's not UTF-8 then that's likely the source of the problem.
>
>                                regards, tom lane
>
>
>