| From: | Craig Ringer <craig(at)2ndquadrant(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-06 07:14:51 |
| Message-ID: | 522980EB.6090204@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 09/05/2013 08:47 PM, Peter Eisentraut wrote:
> Other ideas? Are there legitimate uses for SQL_ASCII?
IMO people who want SQL_ASCII should actually be storing everything in
`bytea`; that's a truer reflection of what they're actually storing,
retrieving, and working with and how they're doing it.
Unfortunately there'll be enough users of it around that I don't think
we can drop it.
What we SHOULD be doing is making it an explicit decision to use
SQL_ASCII, and NEVER creating a cluster or database with that encoding
by default. Ever. If we can't decide what the correct default encoding
is (say, if locale is "C") we should error out unless a specific flag is
set.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2013-09-06 07:23:15 | Re: [PERFORM] encouraging index-only scans |
| Previous Message | wangshuo | 2013-09-06 05:59:19 | Re: Re: [HACKERS] Is it necessary to rewrite table while increasing the scale of datatype numeric？ |