| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joseph Brenner <doomvox(at)gmail(dot)com> |
| Cc: | Daniel Verite <daniel(at)manitou-mail(dot)org>, "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: [HACKERS] Select works only when connected from login postgres |
| Date: | 2016-12-07 20:04:58 |
| Message-ID: | 26963.1481141098@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:
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2016-12-07 21:06:56 | Re: FreeBSD 10 => 11: Dump and reload your PostgreSQL database unless you like it broken |
| Previous Message | Joseph Brenner | 2016-12-07 18:58:56 | Re: [GENERAL] Select works only when connected from login postgres |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2016-12-07 20:09:15 | Re: pg_dump vs. TRANSFORMs |
| Previous Message | Tom Lane | 2016-12-07 20:03:07 | Re: Typmod associated with multi-row VALUES constructs |