Re: [COMMITTERS] pgsql: Improve memory management for external sorts.

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Improve memory management for external sorts.
Date: 2016-03-18 20:22:59
Message-ID: CAM3SWZQ-=KCcrcrjRmN2j181n8d=5ME+AZj9TitQgrPj4QF3nA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Fri, Mar 18, 2016 at 11:43 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> Yes, that removes the warning, and looks correct.

Thanks. We should be careful to not repeat this mistake when the
quicksort patch goes in.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2016-03-18 22:56:58 pgsql: Merge wal_level "archive" and "hot_standby" into new name "repli
Previous Message Tom Lane 2016-03-18 19:06:16 pgsql: Decouple psqlscan.l from surrounding program.

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2016-03-18 20:46:40 Re: Fuzzy substring searching with the pg_trgm extension
Previous Message Robert Haas 2016-03-18 20:11:00 Re: Patch: fix lock contention for HASHHDR.mutex