Well yeah, trying to run a PAGER that's not there might throw an error. Or you know, nothing in PAGER might imply "pager off". > I find it a bit odd that all of your queries were using the pager...did I miss where you reported that setting? I didn't report it because I wasn't looking in that direction. A PAGER set to blank for login 'doom' and no PAGER setting for login 'postgres' explains much of what I was seeing, I think: selects run as 'doom' tended to be blank (unless I had a pset no pager somewhere), selects run as 'postgres' always worked. On Mon, Dec 5, 2016 at 9:03 PM, David G. Johnston <david.g.johnston@xxxxxxxxx> wrote: > On Mon, Dec 5, 2016 at 9:53 PM, Joseph Brenner <doomvox@xxxxxxxxx> wrote: >> >> And I guess I did that intentionally, my .bashrc has >> >> # I use emacs shells, I got a "pager" already: >> export PAGER='' >> > > PAGER= psql --pset=pager=always -c 'select 1;' > <nothing on the screen> > > Remove PAGER= and I'm good. > > I guess that psql could be a bit more helpful by reporting something to > stderr if the value of PAGER is not an executable (platform dependent...) > > I find it a bit odd that all of your queries were using the pager...did I > miss where you reported that setting? > > David J. > -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
