| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Cc: | John Naylor <johncnaylorls(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Non-compliant SASLprep implementation for ASCII characters |
| Date: | 2026-04-13 00:12:32 |
| Message-ID: | adw08BVL9DW7kY4c@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Apr 12, 2026 at 04:00:00PM +0300, Alexander Lakhin wrote:
> Maybe it would make sense to find out why skink doesn't detect this (just
> in case there are or will be similar defects hiding) before pushing the
> fix...
Other fixes can also be applied separately, tackled by their
respective committers.
Saying that, I have also done an installcheck with an instance running
with valgrind, and did not spot something popping out. The log file I
have used for the output was looking a bit weird, as if valgrind had
the idea to overwrite some portions of it, so perhaps I have missed
something.
I have fixed this one for now, thanks for the report.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2026-04-13 00:16:29 | Re: Fix pgstat_database.c to honor passed database OIDs |
| Previous Message | David Rowley | 2026-04-12 23:41:40 | Re: Small and unlikely overflow hazard in bms_next_member() |