| From: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Subject: | Re: Is MinMaxExpr really leakproof? |
| Date: | 2018-12-31 17:40:23 |
| Message-ID: | CAMsGm5cZC_5=Ub5GWtCGJEB5t1gtq1cjkFyn-W_pK0cDbubpiw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 31 Dec 2018 at 12:26, Noah Misch <noah(at)leadboat(dot)com> wrote:
>
> bttextcmp() and other varstr_cmp() callers fall afoul of the same
> restriction
> with their "could not convert string to UTF-16" errors
> (
> https://postgr.es/m/CADyhKSXPwrUv%2B9LtqPAQ_gyZTv4hYbr2KwqBxcs6a3Vee1jBLQ%40mail.gmail.com
> ).
> Leaking the binary fact that an unspecified string contains an unspecified
> rare
> Unicode character is not a serious leak, however. Also, those errors
> would be a
> substantial usability impediment if they happened much in practice; you
> couldn't
> index affected values.
>
>
I'm confused. What characters cannot be represented in UTF-16?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-12-31 17:58:01 | Re: Is MinMaxExpr really leakproof? |
| Previous Message | Pavel Stehule | 2018-12-31 17:33:30 | Re: [HACKERS] proposal: schema variables |