From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: get rid of SQL_ASCII? |
Date: | 2013-09-05 12:52:02 |
Message-ID: | CAHyXU0zy4EZsyy1mzrjX5vmeG8T8jbR5n+i+zO7_tEUt4Bd3wQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Sep 5, 2013 at 7:47 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> Can we consider getting rid of the SQL_ASCII server-side "encoding"? I
> don't see any good use for it, and it's often a support annoyance, and
> it leaves warts all over the code. This would presumably be a
> multi-release effort.
>
> As a first step in accommodating users who have existing SQL_ASCII
> databases, we could change SQL_ASCII into a real encoding with
> conversion routines to all other encodings that only convert 7-bit ASCII
> characters. That way, users who use SQL_ASCII as real ASCII or don't
> care could continue to use it. Others would be forced to either set
> SQL_ASCII as the client encoding or adjust the encoding on the server.
>
> On the client side, the default libpq client "encoding" SQL_ASCII would
> be renamed to something like SAME or whatever, so the behavior would
> stay the same.
>
> Other ideas? Are there legitimate uses for SQL_ASCII?
performance?
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2013-09-05 13:13:25 | Re: get rid of SQL_ASCII? |
Previous Message | Peter Eisentraut | 2013-09-05 12:47:32 | get rid of SQL_ASCII? |