Re: Internal error codes triggered by tests

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Michael Paquier <michael(at)paquier(dot)xyz>
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-18 07:37:06
Message-ID: 3127162F-BA40-4870-B910-EDF3FE50EC96@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 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.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andy Fan 2024-07-18 07:55:42 Re: Optimize WindowAgg's use of tuplestores
Previous Message Michael Paquier 2024-07-18 07:29:36 Re: Internal error codes triggered by tests