Re: verbose mode for pg_input_error_message?

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: verbose mode for pg_input_error_message?
Date: 2023-02-26 04:58:17
Message-ID: 20230226045817.GA1244537@nathanxps13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Feb 25, 2023 at 08:07:33PM -0500, Tom Lane wrote:
> Maybe pg_input_error_info()? I tend to agree with Michael that as
> soon as you throw things like the SQLSTATE code into it, "message"
> seems not very apropos. I'm not dead set on that position, though.

pg_input_error_info() seems more descriptive to me. I changed the name to
that in v4.

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

Attachment Content-Type Size
v4-0001-add-details-to-pg_input_error_message-and-rename-.patch text/x-diff 139.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2023-02-26 05:35:22 Re: verbose mode for pg_input_error_message?
Previous Message Julien Rouhaud 2023-02-26 03:05:18 Re: pg_upgrade and logical replication