Re: Patch to document base64 encoding

From: "Karl O(dot) Pinc" <kop(at)meme(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Patch to document base64 encoding
Date: 2019-03-06 13:09:48
Message-ID: 20190306070948.6af8217e@slate.meme.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 5 Mar 2019 23:23:20 -0600
"Karl O. Pinc" <kop(at)meme(dot)com> wrote:

> Added documentation for hex and escape encodings,
> including output formats and what are acceptable
> inputs.

Attached: doc_base64_v6.patch

Added index entries for encode and decode functions
above the encoding documentation. As index entries
are currently generated this does not make any
difference. But this paragraph is very far
from the other encode/decode index targets on
the page.

Regards,

Karl <kop(at)meme(dot)com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein

Attachment Content-Type Size
doc_base64_v6.patch text/x-patch 6.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Paul Guo 2019-03-06 14:06:27 Batch insert in CTAS/MatView code
Previous Message Etsuro Fujita 2019-03-06 13:06:27 Re: bug in update tuple routing with foreign partitions