From: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: controlling psql's use of the pager a bit more |
Date: | 2014-11-13 16:54:56 |
Message-ID: | 1415897696197-5826833.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan wrote
> On 11/13/2014 11:09 AM, Tom Lane wrote:
>> Andrew Dunstan <
> andrew@
> > writes:
>>> I often get annoyed because psql is a bit too aggressive when it decides
>>> whether to put output through the pager, and the only way to avoid this
>>> is to turn the pager off (in which case your next query might dump many
>>> thousands of lines to the screen). I'd like a way to be able to specify
>>> a minumum number of lines of output before psql would invoke the pager,
>>> rather than just always using the terminal window size.
>> Are you saying you'd want to set the threshold to *more* than the window
>> height? Why?
>
>
> Because I might be quite happy with 100 or 200 lines I can just scroll
> in my terminal's scroll buffer, but want to use the pager for more than
> that. This is useful especially if I want to scroll back and see the
> results from a query or two ago.
+1
David J.
--
View this message in context: http://postgresql.nabble.com/controlling-psql-s-use-of-the-pager-a-bit-more-tp5826819p5826833.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2014-11-13 16:57:41 | Re: Doing better at HINTing an appropriate column within errorMissingColumn() |
Previous Message | Alvaro Herrera | 2014-11-13 16:52:08 | Re: pg_basebackup vs. Windows and tablespaces |