Re: Internal error codes triggered by regression tests and user queries, take 2

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: Kirill Reshke <reshkekirill(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 11:00:00
Message-ID: e57c08d0-421d-400b-af64-3fb3d2c794ae@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kirill Reshke 2026-11-01 12:13:26 Re: Internal error codes triggered by regression tests and user queries, take 2
Previous Message Kirill Reshke 2026-11-01 10:01:38 Re: Internal error codes triggered by regression tests and user queries, take 2