Postgres Pro
Downloads
Home   >   mailing lists

pgsql: GIN index build's allocatedMemory counter needs to be long, not - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: GIN index build's allocatedMemory counter needs to be long, not
Date
Msg-id 20071116215006.DC4937540F0@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Tree view 
Log Message:
-----------
GIN index build's allocatedMemory counter needs to be long, not uint32.
Else, in a 64-bit machine with maintenance_work_mem set to above 4Gb,
the counter overflows and we never recognize having reached the
maintenance_work_mem limit.  I believe this explains out-of-memory
failure recently reported by Sean Davis.

This is a bug, so backpatch to 8.2.

Modified Files:
--------------
    pgsql/src/include/access:
        gin.h (r1.14 -> r1.15)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/access/gin.h?r1=1.14&r2=1.15)

pgsql-committers by date:

Previous
From: alvherre@postgresql.org (Alvaro Herrera)
Date:
Subject: pgsql: Fix inconsistent message wording, and split off a couple of
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: GIN index build's allocatedMemory counter needs to be long, not