From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Joseph Brenner <doomvox(at)gmail(dot)com> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [GENERAL] Select works only when connected from login postgres |
Date: | 2016-12-07 02:07:09 |
Message-ID: | 30580.1481076429@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Joseph Brenner <doomvox(at)gmail(dot)com> writes:
> Well, my take would be that if you've taken the trouble to set an
> empty string as the PAGER that means something, and it probably means
> you don't want any pager to be used.
Yeah, on reflection that argument seems pretty persuasive. So I propose
the attached patch.
BTW, I realized while testing this that there's still one gap in our
understanding of what went wrong for you: cases like "SELECT 'hello'"
should not have tried to use the pager, because that would've produced
less than a screenful of data. But that's irrelevant here, because it
can easily be shown that psql doesn't behave nicely if PAGER is set to
empty when it does try to use the pager.
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
psql-fix-for-empty-PAGER.patch | text/x-diff | 2.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-12-07 02:16:27 | Re: FATAL: semctl(999999, 6, SETVAL, 0) failed: Invalid argument |
Previous Message | DrakoRod | 2016-12-07 01:58:16 | FATAL: semctl(999999, 6, SETVAL, 0) failed: Invalid argument |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-12-07 02:19:24 | Re: Separate connection handling from backends |
Previous Message | Greg Stark | 2016-12-07 01:58:19 | Re: Separate connection handling from backends |