pgsql: Further effort at preventing memory map dump from affectingthe

Поиск
Список
Период
Сортировка
От Tom Lane
Тема pgsql: Further effort at preventing memory map dump from affectingthe
Дата
Msg-id E1fDFHA-00011a-IL@gemulon.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Дерево обсуждения 
Further effort at preventing memory map dump from affecting the results.

Rather than elog'ing immediately, push the map data into a preallocated
StringInfo.  Perhaps this will prevent some of the mid-operation
allocations that are evidently happening now.

Discussion: https://postgr.es/m/25495.1524517820@sss.pgh.pa.us

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/ce07aff48f15a2fa4f91bc67efe1cb3cc9c14bcf

Modified Files
--------------
src/backend/port/win32_shmem.c | 34 +++++++++++++++++++++++-----------
1 file changed, 23 insertions(+), 11 deletions(-)

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

Предыдущее
От: Andrew Dunstan
Дата:
Сообщение: Re: pgsql: Prevent infinity and NaN in jsonb/plperl transform
Следующее
От: Tom Lane
Дата:
Сообщение: pgsql: Map and unmap the shared memory block before riskingVirtualFree