| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Cc: | Andreas Karlsson <andreas(at)proxel(dot)se>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Unicode normalization SQL functions |
| Date: | 2020-02-19 20:09:42 |
| Message-ID: | 1842c35f-2933-345c-b69f-03c40937a064@2ndquadrant.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-02-17 20:14, Daniel Verite wrote:
> The comment in full says:
>
> /*
> * unicode_normalize - Normalize a Unicode string to the specified form.
> *
> * The input is a 0-terminated array of codepoints.
> *
> * In frontend, returns a 0-terminated array of codepoints, allocated with
> * malloc. Or NULL if we run out of memory. In frontend, the returned
> * string is palloc'd instead, and OOM is reported with ereport().
> */
>
> It looks like the 2nd occurrence of "frontend" was meant to be "backend".
This was a pre-existing problem, so I have fixed that separately.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2020-02-19 20:10:37 | Re: explain HashAggregate to report bucket and memory stats |
| Previous Message | Tom Lane | 2020-02-19 20:00:40 | Re: Resolving the python 2 -> python 3 mess |