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

From Fabien COELHO
Subject Re: [PATCH v1] Add \echo_stderr to psql
Date
Msg-id alpine.DEB.2.21.1904221943420.29102@lancre
Whole thread Raw
In response to Re: [PATCH v1] Add \echo_stderr to psql  (David Fetter <david@fetter.org>)
List 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.



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: block-level incremental backup
Next
From: Peter Geoghegan
Date:
Subject: Re: Thoughts on nbtree with logical/varwidth table identifiers, v12on-disk representation