Re: tuplesort memory usage: grow_memtuples
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Greg Stark <stark@mit.edu>
Cc: Peter Geoghegan <peter@2ndquadrant.com>, Simon Riggs <simon@2ndquadrant.com>, Jeff Janes <jeff.janes@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2012-11-16T14:11:07Z
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 Thu, Nov 15, 2012 at 2:54 PM, Greg Stark <stark@mit.edu> wrote: > On Thu, Nov 15, 2012 at 7:36 PM, Peter Geoghegan <peter@2ndquadrant.com> wrote: >> On 15 November 2012 19:16, Robert Haas <robertmhaas@gmail.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