| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SCRAM authentication, take three |
| Date: | 2017-02-15 12:27:13 |
| Message-ID: | CAB7nPqQi1J9b07ZGkBXWjjiPRo2=473TQ3R0BDhtVQ-6jHtLGw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 15, 2017 at 7:58 PM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> On 02/09/2017 09:33 AM, Michael Paquier wrote:
>> Now regarding the shape of the implementation for SCRAM, we need one
>> thing: a set of routines in src/common/ to build decompositions for a
>> given UTF-8 string with conversion UTF8 string <=> pg_wchar array, the
>> decomposition and the reordering. The extension attached roughly
>> implements that. What we can actually do as well is have in contrib/ a
>> module that does NFK[C|D] using the base APIs in src/common/. Using
>> arrays of pg_wchar (integers) to manipulate the characters, we can
>> validate and have a set of regression tests that do *not* have to
>> print non-ASCII characters.
>
>
> A contrib module or built-in extra functions to deal with Unicode characters
> might be handy for a lot of things. But I'd leave that out for now, to keep
> this patch minimal.
No problem from me. I'll get something for SASLprep in the shape of
something like the above. It should not take me long.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2017-02-15 12:35:35 | Re: Proposal: GetOldestXminExtend for ignoring arbitrary vacuum flags |
| Previous Message | Amul Sul | 2017-02-15 12:26:20 | Re: Bug in to_timestamp(). |