pgsql: Further effort at preventing memory map dump from affecting the

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Further effort at preventing memory map dump from affecting the
Date: 2018-04-30 20:19:56
Message-ID: E1fDFHA-00011a-IL@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2018-04-30 21:07:19 pgsql: Map and unmap the shared memory block before risking VirtualFree
Previous Message Andrew Dunstan 2018-04-30 19:13:05 Re: pgsql: Prevent infinity and NaN in jsonb/plperl transform