Re: Backend memory dump analysis

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: Backend memory dump analysis
Дата
Msg-id 7d42de85-be63-6f35-cb25-7fa97e4040da@2ndquadrant.com
обсуждение исходный текст
Ответ на Re: Backend memory dump analysis  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On 3/27/18 19:55, Tom Lane wrote:
> Seems reasonable, although I think if you were to delay setting the
> name till the end of that function, you could point to portal->name
> and avoid the extra pstrdup.  Maybe that's useless microoptimization.

done

>> The term CopySetIdentifier has confused me a bit.  (What's a "set
>> identifier"?)  Maybe use CopyAndSetIdentifier?  (We similarly have
>> MemoryContextResetAndDeleteChildren.)
> 
> No objection, do you want to make the change?

and done

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


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

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: Excessive PostmasterIsAlive calls slow down WAL redo
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: [HACKERS] path toward faster partition pruning