Re: verbose mode for pg_input_error_message?

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: verbose mode for pg_input_error_message?
Date: 2023-02-23 18:40:48
Message-ID: 20230223184048.GA470211@nathanxps13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 10, 2023 at 03:41:12PM -0800, Nathan Bossart wrote:
> My vote would be to redefine the existing pg_input_error_message() function
> to return a record, but I recognize that this would inflate the patch quite
> a bit due to all the existing uses in the tests. If this is the only
> argument against this approach, I'm happy to help with the patch.

Here's an attempt at this.

--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com

Attachment Content-Type Size
v2-0001-add-details-to-pg_input_error_message.patch text/x-diff 82.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2023-02-23 18:45:13 Re: Proposal: %T Prompt parameter for psql for current time (like Oracle has)
Previous Message Corey Huinker 2023-02-23 18:39:14 Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size