From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Greg Stark <greg(dot)stark(at)enterprisedb(dot)com> |
Cc: | Bill Moran <wmoran(at)potentialtech(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Why do we let CREATE DATABASE reassign encoding? |
Date: | 2009-04-23 19:10:17 |
Message-ID: | 2512.1240513817@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greg Stark <greg(dot)stark(at)enterprisedb(dot)com> writes:
> So it would still be possible to byass this check by cloning a
> database into SQL_ASCII and then cloning it into the desired encoding?
> Doesn't sound like it really accomplishes much.
Well, it accomplishes preventing stupid encoding violations. The point
came to mind when I saw a post a little bit ago on -general in which
the poster seemed to imagine that CREATE DATABASE would convert
encodings for him. Since that is not happening in the foreseeable
future, I think we need to prevent the system from acting like it
would work.
If we wanted to be entirely anal about this, we could allow SQL_ASCII
destination with a different source encoding, but not the reverse.
However, we currently consider that you're on your own to ensure sanity
when using SQL_ASCII as far as locale goes, so I'm not sure why the
policy would be different for encoding.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2009-04-23 19:27:05 | Re: Why do we let CREATE DATABASE reassign encoding? |
Previous Message | Bill Moran | 2009-04-23 19:07:22 | Re: Why do we let CREATE DATABASE reassign encoding? |