Re: Internal error codes triggered by tests

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Internal error codes triggered by tests
Date: 2024-07-19 02:35:18
Message-ID: ZpnQ5o4YzfSJOvdo@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 18, 2024 at 09:37:06AM +0200, Daniel Gustafsson wrote:
> On 18 Jul 2024, at 09:29, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>> How about using a new error code in class 58, say a
>> ERRCODE_FILE_NAME_TOO_LONG like in the attached?
>> ERRCODE_DUPLICATE_FILE is like that; it exists just for the mapping
>> with EEXIST.
>
> Agreed, that's probably a better option.

Still sounds like a better idea to me after a night of sleep. Would
somebody disagree about this idea? HEAD only, of course.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2024-07-19 02:36:04 Re: Slow catchup of 2PC (twophase) transactions on replica in LR
Previous Message Michael Paquier 2024-07-19 02:23:08 Re: [PATCH] Add additional extended protocol commands to psql: \parse and \bindx