| From: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
|---|---|
| To: | Bernd Helmle <mailings(at)oopsware(dot)de> |
| Cc: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, amul sul <sul_amul(at)yahoo(dot)co(dot)in>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Selecting large tables gets killed |
| Date: | 2014-02-20 10:07:09 |
| Message-ID: | CAFjFpRdK=R+yjUpEzy3thbOMcCgEA+aBigg4qmVL5puqFJYc3A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Feb 20, 2014 at 3:26 PM, Bernd Helmle <mailings(at)oopsware(dot)de> wrote:
>
>
> --On 20. Februar 2014 14:49:28 +0530 Ashutosh Bapat <
> ashutosh(dot)bapat(at)enterprisedb(dot)com> wrote:
>
> If I set some positive value for this variable, psql runs smoothly with
>> any size of data. But unset that variable, and it gets killed. But it's
>> nowhere written explicitly that psql can run out of memory while
>> collecting the result set. Either the documentation or the behaviour
>> should be modified.
>>
>
> Maybe somewhere in the future we should consider single row mode for psql,
> see
>
> <http://www.postgresql.org/docs/9.3/static/libpq-single-row-mode.html>
>
>
That seems a good idea. We will get rid of FETCH_COUNT then, wouldn't we?
> However, i think nobody has tackled this yet, afair.
>
> --
> Thanks
>
> Bernd
>
--
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-02-20 10:18:22 | Re: [bug fix] pg_ctl fails with config-only directory |
| Previous Message | Bernd Helmle | 2014-02-20 09:56:47 | Re: Selecting large tables gets killed |