| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Joseph Brenner <doomvox(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> |
| Subject: | Re: Select works only when connected from login postgres |
| Date: | 2016-12-06 20:27:13 |
| Message-ID: | CAKFQuwZrdYA5jXuHS9CdgSYUDkA+Y-hbZsSGrmcZEEOQs1hX6g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Tue, Dec 6, 2016 at 1:13 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> So what I'm thinking now is that if PAGER is empty or all white space
> then we should not try to use it as a shell command; we can either
> treat the case as "pager off" or as "use default pager". Everything
> else we can leave to the invoked shell to complain about.
>
My pick would be to leave \pset pager to control the on/off nature of the
pager and treat both an unset and an empty string PAGER identically and
solely for the purpose of choosing which pager to use should one be
required.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-12-06 20:33:58 | Re: PDF files: to store in database or not |
| Previous Message | John R Pierce | 2016-12-06 20:23:52 | Re: PDF files: to store in database or not |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-12-06 20:27:51 | Re: WIP: Faster Expression Processing and Tuple Deforming (including JIT) |
| Previous Message | Robert Haas | 2016-12-06 20:27:06 | Re: Push down more full joins in postgres_fdw |