| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Nikolay Shaplov <dhyan(at)nataraj(dot)su> |
| Cc: | Chapman Flack <chap(at)anastigmatix(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>, Kenneth Marshall <ktm(at)rice(dot)edu>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Subject: | Re: The "char" type versus non-ASCII characters |
| Date: | 2022-07-16 17:09:12 |
| Message-ID: | 3892800.1657991352@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Nikolay Shaplov <dhyan(at)nataraj(dot)su> writes:
> This leads me to an idea that may be as we fix "char" behaviour, we should also
> change it's name to something more speaking for itself.
I don't think this is going to happen. It's especially not going to
happen in the back branches. But in any case, what I'm looking for is
the minimum compatibility breakage needed to fix the encoding-unsafety
problem. Renaming the type goes far beyond that. It'd likely break
some client code that examines the system catalogs, for little gain.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Spyridon Dimitrios Agathos | 2022-07-16 18:38:14 | Re: Bug: Reading from single byte character column type may cause out of bounds memory reads. |
| Previous Message | Mladen Gogala | 2022-07-16 16:53:49 | Re: Proposal to introduce a shuffle function to intarray extension |