Re: [HACKERS] Select works only when connected from login postgres
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Joseph Brenner <doomvox@gmail.com>
Cc: Daniel Verite <daniel@manitou-mail.org>,
"David G. Johnston" <david.g.johnston@gmail.com>,
Adrian Klaver <adrian.klaver@aklaver.com>,
"pgsql-general@postgresql.org" <pgsql-general@postgresql.org>,
pgsql-hackers@postgresql.org
Date: 2016-12-07T20:04:58Z
Lists: pgsql-hackers, pgsql-general
Joseph Brenner <doomvox@gmail.com> writes: > I thought I'd reproduced the behavior in an xterm, but I was just > trying again and I don't see it. It does seem that the dumbness of my > dumb terminal is a factor. Evidently. > If I understand the way this works, it could be an even more baffling > behavior if I were using an xterm: with a blank PAGER your output > would disappear only if the select exceeded a certain number of > lines... Yeah, that was exactly the behavior I was seeing before fixing it (the fix is pushed btw). regards, tom lane
Commits
-
Handle empty or all-blank PAGER setting more sanely in psql.
- 1ec5cc025b41 9.2.20 landed
- ccb84dae13c9 9.4.11 landed
- bb39f58f76b4 9.6.2 landed
- 82eb5c514473 9.3.16 landed
- 370c7a863aa7 9.5.6 landed
- 18f8f784cbbf 10.0 landed