Re: PG15 beta1 sort performance regression due to Generation context change
| От | Tomas Vondra |
|---|---|
| Тема | Re: PG15 beta1 sort performance regression due to Generation context change |
| Дата | |
| Msg-id | 007af81a-08a8-42ba-c81f-739dfe98deeb@enterprisedb.com обсуждение |
| Ответ на | Re: PG15 beta1 sort performance regression due to Generation context change (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: PG15 beta1 sort performance regression due to Generation context change
|
| Список | pgsql-hackers |
On 5/23/22 22:47, Tom Lane wrote: > 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? > D'oh! I knew there has to be some flaw in that idea, but I forgot about this chicken-or-egg issue. regards -- Tomas Vondra EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: