Re: [PATCH v1] Add \echo_stderr to psql

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
Cc: David Fetter <david(at)fetter(dot)org>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH v1] Add \echo_stderr to psql
Date: 2019-04-22 07:04:08
Message-ID: alpine.DEB.2.21.1904220902530.29102@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Hello Corey,

>> \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.


In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2019-04-22 07:15:13 Re: standby recovery fails (tablespace related) (tentative patch and discussion)
Previous Message Amit Langote 2019-04-22 05:51:16 Re: pgsql: Allow insert and update tuple routing and COPY for foreign table