Re: tuplesort memory usage: grow_memtuples

From: Greg Stark <stark(at)mit(dot)edu>
To: Peter Geoghegan <peter(at)2ndquadrant(dot)com>
Cc: 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-10-16 21:18:47
Message-ID: CAM-w4HOzHeEwFWCroLJpi2WiLNxsDZL67i65zDfL=iY0E+AcWQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 16, 2012 at 9:47 PM, Peter Geoghegan <peter(at)2ndquadrant(dot)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?

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2012-10-16 21:34:41 Re: tuplesort memory usage: grow_memtuples
Previous Message Peter Geoghegan 2012-10-16 20:47:56 Re: tuplesort memory usage: grow_memtuples