From: Tom Lane <tgl@sss.pgh.pa.us>
To: jian he <jian.universality@gmail.com>
cc: Aaryan Parik <aaryanparik124@gmail.com>, pgsql-hackers@postgresql.org
Subject: Re: [PATCH] psql: Display SQLSTATE macro name in verbose error
 reports
In-reply-to: 
 <CACJufxG62iwtxYi33ebwhTLaE8JnxJhefoygczXOFhuHhvbTvQ@mail.gmail.com>
References: 
 <CAFAL27jsbbRkjj=zwudUU7vpmNHDgRCQXYEv_qx6D9uc7LLYvQ@mail.gmail.com>
 <CACJufxG62iwtxYi33ebwhTLaE8JnxJhefoygczXOFhuHhvbTvQ@mail.gmail.com>
Comments: In-reply-to jian he <jian.universality@gmail.com>
	message dated "Sun, 24 May 2026 09:56:55 +0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <137425.1779736823.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 25 May 2026 15:20:23 -0400
Message-ID: <137426.1779736823@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/137426.1779736823%40sss.pgh.pa.us>
Precedence: bulk

jian he <jian.universality@gmail.com> writes:
> On Sun, May 24, 2026 at 3:18=E2=80=AFAM Aaryan Parik <aaryanparik124@gma=
il.com> wrote:
>> Example output:
>> ERROR:  42601: syntax error at or near "FRO"
>> LINE 1: SELECT * FRO;
>> ^
>> LOCATION:  scanner_yyerror, scan.l:1220
>> SQLSTATE name: ERRCODE_SYNTAX_ERROR

> This seems identical to the patch submitted in the previous email thread=
, [0].

It's not exactly the same: Josh's patch did the dirty work in libpq
not psql.  So this has a somewhat smaller blast radius for client
compatibility problems (but still not zero).  The other comments
I posted in the other thread still apply though.

			regards, tom lane