| From: | Florian Weimer <fweimer(at)redhat(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: get rid of SQL_ASCII? |
| Date: | 2013-09-06 08:30:11 |
| Message-ID: | 52299293.10600@redhat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 09/06/2013 09:14 AM, Craig Ringer wrote:
> 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.
Practically speaking, the escaping gets in the way, and there isn't full
feature parity with TEXT. Regular expression matching seems to be
missing, for instance.
But apart from that, yes, BYTEA would be the more appropriate choice.
--
Florian Weimer / Red Hat Product Security Team
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2013-09-06 10:30:10 | Re: Analysis on backend-private memory usage (and a patch) |
| Previous Message | Cédric Villemain | 2013-09-06 07:45:06 | Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers |