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 12:47:40
Message-ID: CAFBsxsFyPhFQkkX4VN4b1JsYPNV2Amut9d13jhzohhWvN=gzZw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Thu, Aug 17, 2023 at 11:41 AM John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
wrote:
>
>
> 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.

That remains the only new failure in the buildfarm, and it just failed in
the same way again. I'll try to figure out what could be the cause, but if
I don't I'll revert within 24 hours.

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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Nathan Bossart 2023-08-17 14:26:27 pgsql: Add a few recent commits to .git-blame-ignore-revs.
Previous Message John Naylor 2023-08-17 04:41:44 Re: pgsql: Split out tiebreaker comparisons from comparetup_* functions