Re: BUG #12721: psql -a does not preserve empty lines between SELECTs

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: hans(at)matfyz(dot)cz
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #12721: psql -a does not preserve empty lines between SELECTs
Date: 2015-01-31 22:50:41
Message-ID: 24128.1422744641@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I wrote:
> hans(at)matfyz(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2015-01-31 23:00:59 Re: BUG #12721: psql -a does not preserve empty lines between SELECTs
Previous Message Tom Lane 2015-01-31 18:35:00 Re: BUG #12721: psql -a does not preserve empty lines between SELECTs