Re: proposal: unescape_text function - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: proposal: unescape_text function
Date
Msg-id CAFj8pRAkYbLUCc9QBw64LP4NaP-qCmGm3EpU+zyh=BgwZpf_BQ@mail.gmail.com
Whole thread Raw
In response to Re: proposal: unescape_text function  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: proposal: unescape_text function  (Asif Rehman <asifr.rehman@gmail.com>)
List pgsql-hackers


čt 2. 7. 2020 v 17:27 odesílatel Daniel Gustafsson <daniel@yesql.se> napsal:
> On 23 Jun 2020, at 11:51, Pavel Stehule <pavel.stehule@gmail.com> wrote:

> I changed the name to more accurately "unicode_unescape". Patch is assigned

You've made this function return Oid, where it used to be void.  Was that a
copy-paste mistake? Else the code needs fixing as it doesn't return an Oid.

+Oid
+check_unicode_value(pg_wchar c)
+{
+   if (!is_valid_unicode_codepoint(c))
+       ereport(ERROR,
+               (errcode(ERRCODE_SYNTAX_ERROR),
+                errmsg("invalid Unicode escape value")));
+}


yes, it is my error

I am sending fixed patch

Thank you for check

Pavel

cheers ./daniel
Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: cannot restore schema with is not distinct from on hstore since PG 9.6.8
Next
From: Peter Geoghegan
Date:
Subject: Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)