Re: Question on error code selection in conflict detection

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Dilip Kumar <dilipbalaut(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Question on error code selection in conflict detection
Date: 2025-06-11 14:03:10
Message-ID: CA+TgmobpXW3GB-QS_5Uecj3aeeQFcgo+z-PsU8n7pCq1QXBiSQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 10, 2025 at 2:09 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> Can we instead try to use other suitable existing error codes?

Why?

I mean, I'm not 100% against using existing error codes, but I feel
like we might be distorting the meanings of the existing error codes.
If we used new error codes, then people could test for those and know
that they would get exactly these conditions and nothing else.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shlok Kyal 2025-06-11 14:07:49 Re: Skipping schema changes in publication
Previous Message Nathan Bossart 2025-06-11 13:59:42 Re: CHECKPOINT unlogged data