Re: tuplesort memory usage: grow_memtuples

Peter Geoghegan <peter@2ndquadrant.com>

From: Peter Geoghegan <peter@2ndquadrant.com>

To: Greg Stark <stark@mit.edu>

Cc: Robert Haas <robertmhaas@gmail.com>, Simon Riggs <simon@2ndquadrant.com>, Jeff Janes <jeff.janes@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2012-11-15T21:13:22Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Incorporate a couple of recent tuplesort.c improvements into tuplestore.c.
- 2689abf07849 8.2.0 cited

On 15 November 2012 19:54, Greg Stark <stark@mit.edu> wrote:
> The only concern I had was about the behaviour after it did the
> special case. I didn't want it to keep doing the math and trying to
> grow again a little bit every tuple. I think I was leaning to putting
> the magic flag back.

The alternative might just be to add a new constant to the
TupSortStatus enum. That might be more logical.

-- 
Peter Geoghegan       http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services