"buffer too small" or "path too long"? - Mailing list pgsql-hackers

From Kyotaro Horiguchi
Subject "buffer too small" or "path too long"?
Date
Msg-id 20220613.120551.729848632120189555.horikyota.ntt@gmail.com
Whole thread Raw
Responses Re: "buffer too small" or "path too long"?
List pgsql-hackers
Recently we added the error messages "buffer for root directory too
small" and siblings to pg_upgrade.  This means "<new_cluster's
pgdata>/pg_upgrade_output.d" was longer than MAXPGPATH.

I feel that the "root directory" is obscure here, and moreover "buffer
is too small" looks pointless since no user can do something on the
buffer length.  At least I can't read out from the message concretely
what I should do next..

The root cause of the errors is that the user-provided directory path
of new cluster's root was too long.  Anywhich one of the four buffers
is overflowed, it doesn't makes any difference for users and doesn't
offer any further detail to suppoerters/developers.  I see "output
directory path of new cluster too long" clear enough.

Above all, this change reduces the number of messages that need
translation:)

# And the messages are missing trailing line breaks.

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center

Attachment

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns
Next
From: Amit Kapila
Date:
Subject: Re: bogus: logical replication rows/cols combinations