Horton

Re: [PATCH v1] Add \echo_stderr to psql

Fabien COELHO <fabien.coelho@mines-paristech.fr>

View thread View on postgr.es
From: Fabien COELHO <fabien.coelho@mines-paristech.fr>
To: David Fetter <david@fetter.org>
Cc: Corey Huinker <corey.huinker@gmail.com>, PostgreSQL Development <pgsql-hackers@postgresql.org>
Date: 2019-04-22T17:46:18Z
Lists: pgsql-hackers 
>>>>    \warn ...
>>>>    \warning ...
>>>
>>> These two seem about the best to me, drawing from the perl warn command.
>>
>> Yep, I was thinking of perl & gmake. Maybe the 4 letter option is better
>> because its the same length as "echo".
>>
>>> I suppose we could go the bash &2 route here, but I don't want to.
>>
>> I agree on this one.
>
> Please find attached v2, name is now \warn.
>
> How might we test this portably?

TAP testing? see pgbench which has tap test which can test stdout & stderr 
by calling utility command_checks_all, the same could be done with psql.

-- 
Fabien.

Commits

  1. Add \warn command to psql.