Re: tuplesort memory usage: grow_memtuples

From: Alvaro Herrera <alvherre(at)2ndquadrant(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-10-18 15:51:55
Message-ID: 20121018155155.GB3763@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greg Stark escribió:
> 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?

Feel free. Your committer bits should still work.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2012-10-18 15:58:53 Re: PATCH: optimized DROP of multiple tables within a transaction
Previous Message Alvaro Herrera 2012-10-18 15:46:50 Re: BUG #6510: A simple prompt is displayed using wrong charset