Re: PG15 beta1 sort performance regression due to Generation context change - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PG15 beta1 sort performance regression due to Generation context change
Date
Msg-id 1334086.1653338871@sss.pgh.pa.us
Whole thread Raw
In response to Re: PG15 beta1 sort performance regression due to Generation context change  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
Responses Re: PG15 beta1 sort performance regression due to Generation context change  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
List pgsql-hackers
Tomas Vondra <tomas.vondra@enterprisedb.com> writes:
> On 5/20/22 12:01, Heikki Linnakangas wrote:
>> Could the 'context' field be moved from GenerationChunk to GenerationBlock?

> Not easily, because GetMemoryChunkContext() expects the context to be
> stored right before the chunk. In principle we could add "get context"
> callback to MemoryContextMethods, so that different implementations can
> override that.

How would you know which context type to consult for that?

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: allow building trusted languages without the untrusted versions
Next
From: David Rowley
Date:
Subject: Re: PG15 beta1 sort performance regression due to Generation context change