Re: Selecting large tables gets killed

From: Marti Raudsepp <marti(at)juffo(dot)org>
To: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>
Cc: Bernd Helmle <mailings(at)oopsware(dot)de>, 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 11:58:00
Message-ID: CABRT9RDZaRhgP5F-NspF8G4gm85SBtu9+tGzvzfcyAYrsiF0zw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 20, 2014 at 12:07 PM, Ashutosh Bapat
<ashutosh(dot)bapat(at)enterprisedb(dot)com> wrote:
> That seems a good idea. We will get rid of FETCH_COUNT then, wouldn't we?

No, I don't think we want to do that. FETCH_COUNT values greater than
1 are still useful to get reasonably tabulated output without hogging
too much memory. For example:

db=# \set FETCH_COUNT 3
db=# select repeat('a', i) a, 'x'x from generate_series(1,9)i;
a | x
-----+---
a | x
aa | x
aaa | x
aaaa | x
aaaaa | x
aaaaaa | x
aaaaaaa | x
aaaaaaaa | x
aaaaaaaaa | x

Regards,
Marti

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2014-02-20 13:25:35 Another possible corruption bug in 9.3.2 or possibly a known MultiXact problem?
Previous Message MauMau 2014-02-20 11:55:15 Re: [bug fix] pg_ctl fails with config-only directory