Skip site navigation (1) Skip section navigation (2)

Re: tuplesort memory usage: grow_memtuples

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: Peter Geoghegan <peter(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: tuplesort memory usage: grow_memtuples
Date: 2012-11-16 14:11:07
Message-ID: CA+TgmoZQ-1oTpHA6WTf1XzpiFaODw_pCW0uf0jgRGeTqp2A_0A@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, Nov 15, 2012 at 2:54 PM, Greg Stark <stark(at)mit(dot)edu> wrote:
> On Thu, Nov 15, 2012 at 7:36 PM, Peter Geoghegan <peter(at)2ndquadrant(dot)com> wrote:
>> On 15 November 2012 19:16, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>>> So what's next here?  Do you want to work on these issue some more?
>>> Or does Jeff?  I'd like to see this go in, but I'm not sure I have the
>>> bandwidth to do the legwork myself.
>>
>> I'll take another look. No elegant solution immediately occurs to me, though.
>
> The overflow was trivial to fix.

Mmm... how?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


In response to

pgsql-hackers by date

Next:From: Robert HaasDate: 2012-11-16 14:12:21
Subject: Re: tuplesort memory usage: grow_memtuples
Previous:From: Amit KapilaDate: 2012-11-16 14:08:30
Subject: Re: Proposal for Allow postgresql.conf values to be changed via SQL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group