Re: [HACKERS] psql -e and -n flags - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] psql -e and -n flags
Date
Msg-id 24524.949852482@sss.pgh.pa.us
Whole thread Raw
In response to psql -e and -n flags  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: [HACKERS] psql -e and -n flags  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> The suggestion I have is to offer the traditional behaviour with a single
> -e flag, so there's little change for anyone switching from <7.0, and the
> "full" echo mode with two -e flags. I'd then change the flags in the
> regression drivers to -e -e. Comments? Better ideas?

Seems reasonable.

> Furthermore, does anyone have anything to say in defence of the -n ("no
> readline") option? If not, I'd be tempted to "hide" it now, since it may
> be a popular option letter to have available in the future.

readline automatically turns off if the input is not coming from a
terminal, right?  That seems like the only really compelling reason
to have -n (since you wouldn't want script commands filling your
history or being subject to tab-completion).  I suppose someone who
really hated tab-completion might want a way to turn off just that
feature, though --- is there a way?

BTW, if you need one more item for your psql todo list ;-) ... when
looking at EXPLAIN outputs it's possible to get NOTICE messages that
fill many screensful.  It might be nice if NOTICEs went through the
pager like query results do.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] TODO item
Next
From: Don Baccus
Date:
Subject: Re: [HACKERS] psql -e and -n flags