| From: | tgl(at)postgresql(dot)org (Tom Lane) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: GIN index build's allocatedMemory counter needs to be long, not |
| Date: | 2007-11-16 21:50:13 |
| Message-ID: | 20071116215013.146AD7540F0@cvs.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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.
Tags:
----
REL8_2_STABLE
Modified Files:
--------------
pgsql/src/include/access:
gin.h (r1.9 -> r1.9.2.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/access/gin.h?r1=1.9&r2=1.9.2.1)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-11-16 21:55:59 | pgsql: Improve GIN index build's tracking of memory usage by using |
| Previous Message | Tom Lane | 2007-11-16 21:50:06 | pgsql: GIN index build's allocatedMemory counter needs to be long, not |