Re: pgsql: Split out tiebreaker comparisons from comparetup_* functions

From: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
To: John Naylor <john(dot)naylor(at)postgresql(dot)org>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Split out tiebreaker comparisons from comparetup_* functions
Date: 2023-08-17 04:41:44
Message-ID: CAFBsxsEKEmzxwva9OpZOTAEsVFeXJYzhjfajuAZ+Vhaa=Oc7og@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Wed, Aug 16, 2023 at 5:17 PM John Naylor <john(dot)naylor(at)postgresql(dot)org>
wrote:
>
> Split out tiebreaker comparisons from comparetup_* functions

Hammerkop is getting OOM errors with this change. Most grand totals in the
memory context stats show between 1 and 3 MB, and "tuplesort main" only
shows small-ish requests, so not sure what's going on.

--
John Naylor
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message John Naylor 2023-08-17 12:47:40 Re: pgsql: Split out tiebreaker comparisons from comparetup_* functions
Previous Message Thomas Munro 2023-08-17 04:21:37 pgsql: Remove traces of Sun -lposix4.