From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Daniel Verite <daniel@manitou-mail.org>
Cc: Andreas Karlsson <andreas@proxel.se>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Unicode normalization SQL functions
Date: Wed, 19 Feb 2020 21:09:42 +0100
Message-ID: <1842c35f-2933-345c-b69f-03c40937a064@2ndquadrant.com> (raw)
In-Reply-To: <dd16d2c4-e7cb-4e6d-a92d-40e8dc1cf8a6@manitou-mail.org>
References: <dd16d2c4-e7cb-4e6d-a92d-40e8dc1cf8a6@manitou-mail.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, daniel@manitou-mail.org, andreas@proxel.se
Subject: Re: Unicode normalization SQL functions
In-Reply-To: <1842c35f-2933-345c-b69f-03c40937a064@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox