Patch to document base64 encoding - Mailing list pgsql-hackers

From Karl O. Pinc
Subject Patch to document base64 encoding
Date
Msg-id 20190304163347.7bca4897@slate.meme.com
Whole thread Raw
Responses Re: Patch to document base64 encoding
List pgsql-hackers
Hi,

Doc patch, against master.  Documents encode() and decode() base64
format.

Builds for me.

Attached: doc_base64_v1.patch

References RFC2045 section 6.8 to define base64.

Because encode() and decode() show up in both the string
functions section and the binary string functions section
I documented in only the string functions section and hyperlinked
"base64" in both sections to the new text.


Note that XML output can also generate base64 data.  I suspect
this is done via the (different, src/common/base64.c)
pg_b64_encode() function which does not limit line length.  
In any case this patch does not touch the XML documentation.

Regards,

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

Attachment

pgsql-hackers by date:

Previous
From: "Bossart, Nathan"
Date:
Subject: Re: reloption to prevent VACUUM from truncating empty pages at theend of relation
Next
From: Tom Lane
Date:
Subject: Re: Rare SSL failures on eelpout