| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Kirill Reshke <reshkekirill(at)gmail(dot)com>, Alexander Lakhin <exclusion(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, 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 17:09:37 |
| Message-ID: | 369161.1793552977@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2026-11-01 17:13:26 +0500, Kirill Reshke wrote:
>> 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?
The reason was mentioned at the top of the thread: some people monitor
their logs for XX000 errors. I agree that we can't afford to spend
a lot of effort on this, but fixing easily-reached cases seems like a
reasonable thing to do, IMO.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2026-11-01 17:27:35 | Re: [PATCH] Refactor pgbench to make future improvements easier |
| Previous Message | Tom Lane | 2026-11-01 16:27:41 | Re: [PG19] Bogus errors for polymorphic plpython functions |