| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
| 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-17 14:11:48 |
| Message-ID: | 31BB7C38-5B75-4C02-BC59-73FF6331C591@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 16 Jul 2026, at 15:36, David E. Wheeler <david(at)justatheory(dot)com> wrote:
>
> 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.
Pushed, thanks for review!
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Masterov | 2026-07-17 14:15:15 | Re: Unexpected behavior after OOM errors |
| Previous Message | Álvaro Herrera | 2026-07-17 14:08:23 | Re: Caching a partition index's parent OID in the relcache? |