From: Michael Paquier <michael@paquier.xyz>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Add new error code for "file name too long"
Date: Mon, 22 Jul 2024 00:32:10 +0000
Message-ID: <E1sVgyI-000cht-IJ@gemulon.postgresql.org> (raw)
Add new error code for "file name too long"
This new error code, named file_name_too_long, maps internally to the
errno ENAMETOOLONG to produce a proper error code rather than an
internal code under errcode_for_file_access(). This error code can be
reached with some SQL command patterns, like a snapshot file name.
Reported-by: Alexander Lakhin
Reviewed-by: Daniel Gustafsson
Discussion: https://postgr.es/m/Zo4ROR9mgy8bowMo@paquier.xyz
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/2d8ef5e24fd3d38ffc2379ca32eaeef8c9eee1a7
Modified Files
--------------
src/backend/utils/errcodes.txt | 1 +
src/backend/utils/error/elog.c | 4 ++++
2 files changed, 5 insertions(+)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: michael@paquier.xyz, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Add new error code for "file name too long"
In-Reply-To: <E1sVgyI-000cht-IJ@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox