Re: BUG #12721: psql -a does not preserve empty lines between SELECTs - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #12721: psql -a does not preserve empty lines between SELECTs
Date
Msg-id 24128.1422744641@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #12721: psql -a does not preserve empty lines between SELECTs  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #12721: psql -a does not preserve empty lines between SELECTs  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
I wrote:
> hans@matfyz.cz writes:
>> There is, in the [doc] that psql with option -a echoes all input lines.

> Hm.  That's poorly phrased: what it actually echoes is commands, not
> lines.  This must be so because some of the other possible settings of
> ECHO require decisions at the per-command level.

Huh --- I take that back; the "queries" and "errors" cases are implemented
totally independently of "all" mode.  The "all" mode does work on a line
by line basis, and there's no good reason why it doesn't print blank
lines, except that somebody wasn't thinking very hard about where they
added the test.  Will fix.

The documentation is wrong too, but not in the way I thought; it should
say that interactive input is never echoed by this feature, rather than
that it's "less useful" to turn it on for that.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #12721: psql -a does not preserve empty lines between SELECTs
Next
From: Tom Lane
Date:
Subject: Re: BUG #12721: psql -a does not preserve empty lines between SELECTs