| From: | Kirill Reshke <reshkekirill(at)gmail(dot)com> |
|---|---|
| To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Subject: | Re: Internal error codes triggered by regression tests and user queries, take 2 |
| Date: | 2026-11-01 12:13:26 |
| Message-ID: | CALdSSPiZr8_-CSE4zuuss=332rfxQMgU6gW39_si8kDzabB8bA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, 1 Nov 2026 at 16:00, Alexander Lakhin <exclusion(at)gmail(dot)com> wrote:
>
> Hello Kirill,
>
> 01.11.2026 12:01, Kirill Reshke wrote:
> > I run some fuzzing after you reply in [0]. There are results .
>
> Thank you for working on this! I encountered several of these cases before,
> but didn't report them, e.g. operator-related because of [1]. But yes,
> contrib/ has a lot of user-reachable elog(ERRORs)...
>
> Probably the list needs filtering, according to the above discussion.
>
> [1] https://www.postgresql.org/message-id/Zo4ROR9mgy8bowMo%40paquier.xyz
>
> Best regards,
> Alexander
Yeah, I had a hunch that most of this wouldn't be fixed. But reading
the thread from your link, I put it in simple rule : code area is
little maintained -> no care, otherwise all sql-reachable errors
should not be XX000.
Filtering my report with this rule, I think we need to take care of 4-7, 11, 13
--
Best regards,
Kirill Reshke
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Lakhin | 2026-11-01 13:00:00 | 007_pre_auth.pl fails if injection_points_wakeup hits unintended process |
| Previous Message | Alexander Lakhin | 2026-11-01 11:00:00 | Re: Internal error codes triggered by regression tests and user queries, take 2 |