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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: didier <did447(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Pavel Stěhule <pavel(dot)stehule(at)gmail(dot)com>, 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: 2019-02-04 01:54:13
Message-ID: 20190204015413.GJ1881@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

On Mon, Jan 07, 2019 at 10:44:24PM +0100, didier wrote:
> On Sat, Jan 5, 2019 at 6:30 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
>>> Why are you not including a test for \set VERBOSITY verbose?
>>
>> Stability of the output would be a problem ...
>>
>> Yes it could moreover the functionality wasn't tested before.
> Should I add one ?

Unpredictible outputs mean more maintenance and more alternate
outputs. I have moved the patch to next CF, still ready for
committer.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-02-04 01:55:38 Re: psql display of foreign keys
Previous Message Michael Paquier 2019-02-04 01:51:32 Re: DECLARE STATEMENT Syntax support