| From: | Alan Nilsson <anilsson(at)apple(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Tim Kane <tim(dot)kane(at)gmail(dot)com>, Suzuki Hironobu <hironobu(at)interdb(dot)jp>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: psql client memory usage |
| Date: | 2013-09-09 20:56:33 |
| Message-ID: | 408F5BB4-2CEC-4857-B8BB-01C84648F3A2@apple.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sep 6, 2013, at 6:56 AM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> On Fri, Sep 6, 2013 at 8:19 AM, Tim Kane <tim(dot)kane(at)gmail(dot)com> wrote:
>> Ahh. All these years (albeit sporadic), I never knew about FETCH_COUNT.
>> That makes sense. Thanks muchly.
>
> Not your fault: FETCH_COUNT is a hack IMO. The real issue was that
> libpq (until recently) forced the entire result into memory before it
> was returned to the caller. We can now in libpq (thanks Marko) that
> allows process rows as they come in. I expect soon psql will be
> adjusted to utilize that new API (although exactly how is unclear);
what version did/does this come into effect?
alan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ryan Kelly | 2013-09-09 21:05:37 | Re: psql client memory usage |
| Previous Message | patrick keshishian | 2013-09-09 20:52:31 | Re: Call for design: PostgreSQL mugs |