| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
| Cc: | chriskl(at)familyhealth(dot)com(dot)au, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: encoding question |
| Date: | 2003-04-17 01:20:48 |
| Message-ID: | 20030417.102048.41633402.t-ishii@sra.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> writes:
> > What is the encoding of the database names in pg_database???
>
> I suspect we do not have a consistent answer to that :-( ... it
> probably depends on which database you did CREATE DATABASE from ...
Right. Usually encodings for global tables such as pg_database are
same as template1 unless you explicitly specify the template
database. Since PostgreSQL does not allow tables where each row is
encoded differently(even the standard does allow that), you should use
characters that are common among all possible encodings for such
global tables. This means you could only use ASCII for database
names. Same thing can be said for user names.
--
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2003-04-17 01:21:24 | Re: GLOBAL vs LOCAL temp tables |
| Previous Message | Ron Mayer | 2003-04-16 22:38:31 | Re: Are we losing momentum? |