| From: | "Karl O(dot) Pinc" <kop(at)meme(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Subject: | Re: Patch to document base64 encoding |
| Date: | 2019-03-09 20:53:52 |
| Message-ID: | 20190309145352.6cf40494@slate.meme.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Fabien (and Michael),
On Wed, 6 Mar 2019 16:37:05 -0600
"Karl O. Pinc" <kop(at)meme(dot)com> wrote:
> I'm confident that the behavior I documented is how PG behaves
> but you should know what I did in case you want further
> validation.
>
> Attached: doc_base64_v8.patch
FYI. To avoid a stall in the patch submission process.
I notice that nobody has signed up as a reviewer for
this patch. When the patch looks "ready" it needs
to be marked as such at the PG commitfest website
and a committer will consider committing.
The commitfest URL is:
https://commitfest.postgresql.org/23/
No rush.
Regards,
Karl <kop(at)meme(dot)com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-03-09 21:04:39 | Re: Should we increase the default vacuum_cost_limit? |
| Previous Message | Gavin Flower | 2019-03-09 20:36:59 | Re: Should we increase the default vacuum_cost_limit? |