Re: verbose mode for pg_input_error_message? - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: verbose mode for pg_input_error_message?
Date
Msg-id Y/mQ+VWjiyHK2jd1@paquier.xyz
Whole thread Raw
In response to Re: verbose mode for pg_input_error_message?  (Corey Huinker <corey.huinker@gmail.com>)
Responses Re: verbose mode for pg_input_error_message?
List pgsql-hackers
On Fri, Feb 24, 2023 at 05:36:42PM -0500, Corey Huinker wrote:
> Looks good to me, passes make check-world. Thanks for slogging through this.

FWIW, I agree that switching pg_input_error_message() to return a row
would be nicer in the long-run than just getting an error message
because it has the merit to be extensible at will with all the data
we'd like to attach to it (I suspect that getting more fields is not
much likely, but who knows..).

pg_input_error_message() does not strike me as a good function name,
though, because it now returns much more than an error message.
Hence, couldn't something like pg_input_error() be better, because
more generic?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Kirk Wolak
Date:
Subject: Re: Proposal: :SQL_EXEC_TIME (like :ROW_COUNT) Variable (psql)
Next
From: Michael Paquier
Date:
Subject: Re: zstd compression for pg_dump