Re: Reducing the chunk header sizes on all memory context types
От | Tomas Vondra |
---|---|
Тема | Re: Reducing the chunk header sizes on all memory context types |
Дата | |
Msg-id | b48f3a16-9e11-7663-3083-f2d28b4184f8@enterprisedb.com обсуждение исходный текст |
Ответ на | Re: Reducing the chunk header sizes on all memory context types (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Reducing the chunk header sizes on all memory context types
|
Список | pgsql-hackers |
On 8/29/22 23:57, Tom Lane wrote: > David Rowley <dgrowleyml@gmail.com> writes: >> I've read over the emails and glanced at Tomas' patch. I think that >> seems good. I think I'd rather see us do that than pad the struct out >> further as Tomas' method is more aligned to what we do in aset.c >> (ALLOC_BLOCKHDRSZ) and generation.c (Generation_BLOCKHDRSZ). > >> I can adjust Tomas' patch to #define Slab_BLOCKHDRSZ > > WFM > Same here. I also suggested doing a similar check in MemoryChunkGetPointer, so that we catch the issue earlier - right after we allocate the chunk. Any opinion on that? With an assert only in GetMemoryChunkMethodID() we'd notice the issue much later, when it may not be obvious if it's a memory corruption or what. But maybe it's overkill. regards -- Tomas Vondra EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: