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: 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-01-07 21:44:24
Message-ID: CAJRYxuLELz1mgEK0VjwPx8D7ku66r8F7xi-DjAADcOjLhcyUuw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 ?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2019-01-07 22:06:20 GSoC 2019
Previous Message Tom Lane 2019-01-07 21:11:04 Re: reducing the footprint of ScanKeyword (was Re: Large writable variables)