| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Florents Tselai <florents(dot)tselai(at)gmail(dot)com>, Aleksander Alekseev <aleksander(at)tigerdata(dot)com>, Cary Huang <cary(dot)huang(at)highgo(dot)ca>, Przemysław Sztoch <przemyslaw(at)sztoch(dot)pl>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Subject: | Re: encode/decode support for base64url |
| Date: | 2026-07-16 13:36:39 |
| Message-ID: | BC06CE7A-52C7-4061-8E75-291D8E82F96E@justatheory.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jul 16, 2026, at 09:19, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> During postcommit review for the upcoming v19 release I realized that this
> introduced a slight regression in the truncation rules for plain base64. The
> checks for padding must check the format to make sure it's a base64url, as per
> the attached.
+1, though it’d be nice to have a base64 variant that didn’t require trailing `=`s. Or one that could omit the newlines. Not for now, of course.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rafia Sabih | 2026-07-16 13:37:17 | Re: Allow table AMs to define their own reloptions |
| Previous Message | Daniel Gustafsson | 2026-07-16 13:19:39 | Re: encode/decode support for base64url |