Re: tuplesort memory usage: grow_memtuples
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.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-10-18T15:51:55Z
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
Greg Stark escribió: > On Tue, Oct 16, 2012 at 9:47 PM, Peter Geoghegan <peter@2ndquadrant.com> wrote: > > The patch will now been marked "ready for committer". Does this need > > doc changes, in light of what is arguably a behavioural difference? > > You only mentioned release notes. > > I'm happy to look at this one, probably next week at pgconf.eu. It seems like a > reasonable size patch to get back into things. > > That's assuming my committer bits haven't lapsed and people are ok > with me stepping back into things? Feel free. Your committer bits should still work. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services