Re: PATCH: Add uri percent-encoding for binary data - Mailing list pgsql-hackers

From Anders Åstrand
Subject Re: PATCH: Add uri percent-encoding for binary data
Date
Msg-id CAPwPebtWSDUh8mCxaWJpYeHH1weN2gwXtamHzLFOqnTkHVmkyA@mail.gmail.com
Whole thread Raw
In response to Re: PATCH: Add uri percent-encoding for binary data  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Thanks for keeping this alive even though I disappeared after submitting it!

I can write documentation this weekend.

Thanks again.
//Anders

On Thu, 20 Feb 2020, 23:28 Alvaro Herrera, <alvherre@2ndquadrant.com> wrote:
On 2019-Oct-07, Anders Åstrand wrote:

> Attached is a patch for adding uri as an encoding option for
> encode/decode. It uses what's called "percent-encoding" in rfc3986
> (https://tools.ietf.org/html/rfc3986#section-2.1).

Thanks.  Seems useful.  I made a few cosmetic tweaks and it looks almost
ready to me; however, documentation is missing.  I added a stub; can you
please complete that?

To answer Arthur Zakirov's question: yes, the standard recommends
("should") to use uppercase characters:

:  For consistency, URI producers and
:  normalizers should use uppercase hexadecimal digits for all percent-
:  encodings.

Thanks,

--
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Add PGURI env var for passing connection string to psql in Docker
Next
From: Michael Paquier
Date:
Subject: Re: [Patch] Make pg_checksums skip foreign tablespace directories