| From: | tgl(at)svr1(dot)postgresql(dot)org (Tom Lane) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: When using C-string lookup keys in a dynahash.c hash table, use |
| Date: | 2005-06-18 20:52:00 |
| Message-ID: | 20050618205200.0E5DB5280D@svr1.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Log Message:
-----------
When using C-string lookup keys in a dynahash.c hash table, use strncpy()
not memcpy() to copy the offered key into the hash table during HASH_ENTER.
This avoids possible core dump if the passed key is located very near the
end of memory. Per report from Stefan Kaltenbrunner.
Tags:
----
REL7_4_STABLE
Modified Files:
--------------
pgsql/src/backend/utils/hash:
dynahash.c (r1.48 -> r1.48.2.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/hash/dynahash.c.diff?r1=1.48&r2=1.48.2.1)
pgsql/src/include/utils:
hsearch.h (r1.29 -> r1.29.2.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/hsearch.h.diff?r1=1.29&r2=1.29.2.1)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James William Pye | 2005-06-18 21:15:32 | python - be: Check NULL tb, rather than tbstr. |
| Previous Message | Tom Lane | 2005-06-18 20:51:44 | pgsql: When using C-string lookup keys in a dynahash.c hash table, use |