Re: PG15 beta1 sort performance regression due to Generation context change

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG15 beta1 sort performance regression due to Generation context change
Date: 2022-05-25 01:23:07
Message-ID: 1773241.1653441787@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2022-05-24 12:01:58 -0400, Tom Lane wrote:
>> For back-patching into v14, we could put the new NodeTag type at the
>> end of that enum list. The change in the inline GetMemoryChunkContext
>> is probably an acceptable hazard.

> Why would we backpatch this to 14? I don't think we have any regressions
> there?

Oh, sorry, I meant v15. I'm operating on the assumption that we have
at least a weak ABI freeze in v15 already.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-05-25 01:24:39 Re: "ERROR: latch already owned" on gharial
Previous Message Michael Paquier 2022-05-25 01:20:55 Re: Assert name/short_desc to prevent SHOW ALL segfault