Re: [PATCH v4] Add \warn to psql
David Fetter <david@fetter.org>
From: David Fetter <david@fetter.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Arthur Zakirov <a.zakirov@postgrespro.ru>, Fabien COELHO <coelho@cri.ensmp.fr>, Corey Huinker <corey.huinker@gmail.com>, PostgreSQL Development <pgsql-hackers@postgresql.org>
Date: 2019-07-05T21:29:03Z
Lists: pgsql-hackers
On Fri, Jul 05, 2019 at 12:38:02PM -0400, Tom Lane wrote: > I wrote: > > David Fetter <david@fetter.org> writes: > >> [ v7-0001-Add-warn-to-psql.patch ] > > > I took a look at this. I have no quibble with the proposed feature, > > and the implementation is certainly simple enough. But I'm unconvinced > > about the proposed test scaffolding. > > I pushed this with the simplified test methodology. Thanks! > While I was fooling with it I noticed that the existing code for -n > is buggy. The documentation says clearly that only the first > argument is a candidate to be -n: > > If the first argument is an unquoted <literal>-n</literal> the trailing > newline is not written. > > but the actual implementation allows any argument to be recognized as > -n: > > regression=# \echo this -n should not be -n like this > this should not be like thisregression=# > > I fixed that, but I'm wondering if we should back-patch that fix > or leave the back branches alone. +0.5 for back-patching. Best, David. -- 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
Commits
-
Add \warn command to psql.
- 02e95a5049f7 13.0 landed