Re: [PATCH v1] Add \echo_stderr to psql

From: Fabien COELHO <fabien(dot)coelho(at)mines-paristech(dot)fr>
To: David Fetter <david(at)fetter(dot)org>
Cc: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH v1] Add \echo_stderr to psql
Date: 2019-04-22 17:46:18
Message-ID: alpine.DEB.2.21.1904221943420.29102@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
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.


In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2019-04-22 17:47:07 Re: Thoughts on nbtree with logical/varwidth table identifiers, v12 on-disk representation
Previous Message Robert Haas 2019-04-22 17:44:25 Re: block-level incremental backup