Thanks to visit codestin.com
Credit goes to postgrespro.com

Request a Demo
Home   >   mailing lists

pgsql: Improve GIN index build's tracking of memory usage by using - Mailing list pgsql-committers

From [email protected] (Tom Lane)
Subject pgsql: Improve GIN index build's tracking of memory usage by using
Date
Msg-id [email protected]
Whole thread Raw
List pgsql-committers
Tree view 
Log Message:
-----------
Improve GIN index build's tracking of memory usage by using
GetMemoryChunkSpace, not just the palloc request size.  This brings the
allocatedMemory counter close enough to reality (as measured by
MemoryContextStats printouts) that I think we can get rid of the arbitrary
factor-of-2 adjustment that was put into the code initially.  Given the
sensitivity of GIN build to work memory size, not using as much of work
memory as we're allowed to seems a pretty bad idea.

Modified Files:
--------------
    pgsql/src/backend/access/gin:
        ginbulk.c (r1.9 -> r1.10)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/ginbulk.c?r1=1.9&r2=1.10)
        gininsert.c (r1.9 -> r1.10)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/gininsert.c?r1=1.9&r2=1.10)

pgsql-committers by date:

Previous
From: [email protected] (Tom Lane)
Date:
Subject: pgsql: GIN index build's allocatedMemory counter needs to be long, not
Next
From: [email protected] (User Dpage)
Date:
Subject: stackbuilder - installers: Update for Slony 1.2.12