Re: [PATCH v1] Add \echo_stderr to psql - Mailing list pgsql-hackers

From David Fetter
Subject Re: [PATCH v1] Add \echo_stderr to psql
Date
Msg-id 20190421213819.GA4688@fetter.org
Whole thread Raw
In response to Re: [PATCH v1] Add \echo_stderr to psql  (Fabien COELHO <coelho@cri.ensmp.fr>)
List 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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: ALTER TABLE with ADD COLUMN and ADD PRIMARY KEY USING INDEX throws spurious "column contains null values"
Next
From: Michał "phoe" Herda
Date:
Subject: Allow any[] as input arguments for sql/plpgsql functions to mimicformat()