Re: [proposal] Add an option for returning SQLSTATE in psql error message

From: didier <did447(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: andrew(at)tao11(dot)riddles(dot)org(dot)uk, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [proposal] Add an option for returning SQLSTATE in psql error message
Date: 2018-12-03 17:57:32
Message-ID: CAJRYxuKqFn-E-W-beC25dv7614u0Uo_YCXukTJREd8RG_9ibZw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

On Mon, Dec 3, 2018 at 5:51 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> No, it's in libpq, so you'd have to touch that not the server.
libpq, not as bad as the server but nonetheless maybe a bit too much for this.
Is adding value in library contract?

Anyway. attached a POC adding a new value to VERBOSITY (hopefully
nobody is using it).

Attachment Content-Type Size
master_verbosity_sqlstate.diff text/x-patch 2.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2018-12-03 18:01:28 Re: [proposal] Add an option for returning SQLSTATE in psql error message
Previous Message Alvaro Herrera 2018-12-03 17:17:25 Re: [HACKERS] CLUSTER command progress monitor