Re: [PATCH v1] Add \echo_stderr to psql

From: David Fetter <david(at)fetter(dot)org>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH v1] Add \echo_stderr to psql
Date: 2019-04-21 21:38:20
Message-ID: 20190421213819.GA4688@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Apr 21, 2019 at 09:31:16PM +0200, Fabien COELHO wrote:
> > Any interest in this?
>
> Yep, although I'm not sure of the suggested command name. More suggestions:
> \stderr ...
> \err ...
> \error ...
> \warn ...
> \warning ...

Naming Things is one of the two[1] hard problems in CS.

I'm happy with whatever the community consensus comes out to be.

Best,
David.

[1] The others are cache coherency and off-by-one
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michał phoe Herda 2019-04-21 22:03:06 Allow any[] as input arguments for sql/plpgsql functions to mimic format()
Previous Message Tom Lane 2019-04-21 21:21:28 Re: ALTER TABLE with ADD COLUMN and ADD PRIMARY KEY USING INDEX throws spurious "column contains null values"