1berry/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add a comment noting that heap_copytuple_with_tuple() results in a

Browse Source 
HeapTuple that is no longer allocated as a single palloc() block; if
used carelessly, this might result in a subsequent memory leak after
heap_freetuple().
This commit is contained in:
Neil Conway 2006-11-23 05:27:18 +00:00
parent 0c6f167c4a
commit 546d6848ca
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/backend/access/common/heaptuple.c
View File

@ -16,7 +16,7 @@
* *
* *
* IDENTIFICATION * IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/access/common/heaptuple.c,v 1.111 2006/10/04 00:29:47 momjian Exp $ * $PostgreSQL: pgsql/src/backend/access/common/heaptuple.c,v 1.112 2006/11/23 05:27:18 neilc Exp $
* *
*------------------------------------------------------------------------- *-------------------------------------------------------------------------
*/ */
@ -631,6 +631,9 @@ heap_copytuple(HeapTuple tuple)
* heap_copytuple_with_tuple * heap_copytuple_with_tuple
* *
* copy a tuple into a caller-supplied HeapTuple management struct * copy a tuple into a caller-supplied HeapTuple management struct
*
* Note that after calling this function, the "dest" HeapTuple will not be
* allocated as a single palloc() block (unlike with heap_copytuple()).
* ---------------- * ----------------
*/ */
void void