| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_database encoding again |
| Date: | 2003-06-02 04:11:31 |
| Message-ID: | 1425.1054527091@sss.pgh.pa.us |
| 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 the pg_database table? As far
> as I can tell, each row is saved in the encoding of the database from which
> it is created?
That sounds about right. If you're using databases of different
encodings in the same installation, it would probably be wise to
restrict yourself to the intersection of those encodings when choosing
database names.
I agree that this isn't ideal, but I don't see any way to improve it.
If you like, we could put in code to *enforce* a restriction to 7-bit
ASCII in database names (and user and group names too) ... but that
doesn't seem like a big improvement.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2003-06-02 04:33:23 | Re: pg_database encoding again |
| Previous Message | Bruce Momjian | 2003-06-02 03:51:15 | Re: Why are triggers semi-deferred? |