| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | John DeSoi <desoi(at)pgedit(dot)com> |
| Cc: | Raimon Fernandez <coder(at)montx(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: MD5 Authentication |
| Date: | 2009-11-06 06:14:39 |
| Message-ID: | 29111.1257488079@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
John DeSoi <desoi(at)pgedit(dot)com> writes:
> ... But it is unclear to me what happens when
> the user or database name has non-ascii characters. The client
> encoding is not established until after authentication.
No encoding conversion will happen on those names. If you consistently
use the same encoding in all clients as in the database, there's no
problem in using non-ASCII user or DB names. If not, I'd recommend
sticking to ASCII.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | A.Bhattacharya | 2009-11-06 06:42:58 | PostgreSQL for 64 Bit Windows Version |
| Previous Message | Scott Marlowe | 2009-11-06 06:05:32 | Re: Re: Bench marking performance or experience using Solid State Disk Drives (SSD) with postgres |