From: | Joseph Brenner <doomvox(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Select works only when connected from login postgres |
Date: | 2016-12-06 04:52:37 |
Message-ID: | CAFfgvXVOpGHhCzQLkEy-LGt-6oQKnuzauaP_dBZJY4PdkMPWvw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Wait, that's not quite right. The user 'postgres' has no PAGER envar,
but user 'doom' has an empty value:
PAGER=
On Mon, Dec 5, 2016 at 8:50 PM, Joseph Brenner <doomvox(at)gmail(dot)com> wrote:
>> So what does:
>>
>> env | grep PAGER
>>
>> show?
>
> Nothing. I have no PAGER settting (I don't normally use one).
>
>
> On Mon, Dec 5, 2016 at 5:33 PM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>> On 12/05/2016 05:13 PM, Joseph Brenner wrote:
>>
>>
>>> I just went around temporarily undoing things I did while
>>> straigtening up, and I find there's one thing I can do that
>>> consistently breaks things: removing my new ~/.psqlrc file.
>>> In fact, it appears that I need to have a file that exists and
>>> contains this line:
>>>
>>> \pset pager off
>>
>>
>> So what does:
>>
>> env | grep PAGER
>>
>> show?
>>
>>
>>
>>
>> --
>> Adrian Klaver
>> adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Joseph Brenner | 2016-12-06 04:53:41 | Re: Select works only when connected from login postgres |
Previous Message | Joseph Brenner | 2016-12-06 04:50:42 | Re: Select works only when connected from login postgres |
From | Date | Subject | |
---|---|---|---|
Next Message | Joseph Brenner | 2016-12-06 04:53:41 | Re: Select works only when connected from login postgres |
Previous Message | Joseph Brenner | 2016-12-06 04:50:42 | Re: Select works only when connected from login postgres |