Re: Rethinking MemoryContext creation

Поиск
Список
Период
Сортировка
От Simon Riggs
Тема Re: Rethinking MemoryContext creation
Дата
Msg-id CANP8+j+8iJncp6c1Fr04rgNoh-Hx-ao7fkiGUENOkhrG1BO0-A@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Rethinking MemoryContext creation  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On 11 December 2017 at 17:38, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Simon Riggs <simon@2ndquadrant.com> writes:
>> On 11 December 2017 at 16:27, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> For a *very* large majority of the callers of AllocSetContextCreate,
>>> the context name is a simple C string constant, so we could just store
>>> the pointer to it and save the space and cycles required to copy it.
>
>> Why have the string at all in that case?
>
> Try reading a MemoryContextStats dump without it ...

I understood. I thought you were suggesting removing it in favour of a pointer.

-- 
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Amit Langote
Дата:
Сообщение: Re: Boolean partitions syntax
Следующее
От: Amit Kapila
Дата:
Сообщение: README.tuplock seems to have outdated information