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-22 00:45:24
Message-ID: Zp2rpLiB5gsPjaI5@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.

Applied this one now on HEAD. On second look, all buildfarm
environments seem to be OK with this errno, as far as I've checked, so
that should be OK.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2024-07-22 00:52:43 Re: POC, WIP: OR-clause support for indexes
Previous Message Thomas Munro 2024-07-21 23:27:37 Re: xid_wraparound tests intermittent failure.