| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | lejeczek <peljasz(at)yahoo(dot)co(dot)uk>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: What is paging my psql |
| Date: | 2025-11-21 15:16:11 |
| Message-ID: | 2180758.1763738171@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> Whether the pager is used is conditioned on actual output data.
IIRC, you can do "\pset pager always" if you want the pager to be
invoked regardless of the query output length.
Be aware though that the default pager is "more", which (at least
on my Linux box) silently does nothing special if the output is less
than a screenful. If the behavior you are looking for is "wait for
a keystroke even after very short output", you'd need to combine the
\pset setting with "export PSQL_PAGER=less" or similar.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nicolas Ross | 2025-11-21 16:39:04 | Re: Can't update RPM package to latest version |
| Previous Message | Michael Banck | 2025-11-21 13:44:20 | Re: Can't update RPM package to latest version |