| 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:06 |
| Message-ID: | 20071116215006.DC4937540F0@cvs.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-11-16 21:50:13 | pgsql: GIN index build's allocatedMemory counter needs to be long, not |
| Previous Message | Alvaro Herrera | 2007-11-16 21:47:32 | pgsql: Fix inconsistent message wording, and split off a couple of |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-11-16 21:51:31 | Re: [GENERAL] [pgtranslation-translators] Call for translations |
| Previous Message | Peter Eisentraut | 2007-11-16 21:32:43 | Re: [GENERAL] [pgtranslation-translators] Call for translations |