On 2026-11-01 17:13:26 +0500, Kirill Reshke wrote: > On Sun, 1 Nov 2026 at 16:00, Alexander Lakhin <[email protected]> wrote: > > 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
We're quite busy, being flooded with bug reports and ginormous patches. Why are we trying to find even more work by searching for inconsequential stuff like this? I really don't get it. Like, you wrote a fuzzer to search for these. WHY?
