Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit546d684

Browse files
author
Neil Conway
committed
Add a comment noting that heap_copytuple_with_tuple() results in a
HeapTuple that is no longer allocated as a single palloc() block; ifused carelessly, this might result in a subsequent memory leak afterheap_freetuple().
1 parent0c6f167 commit546d684

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

‎src/backend/access/common/heaptuple.c

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@
1616
*
1717
*
1818
* IDENTIFICATION
19-
* $PostgreSQL: pgsql/src/backend/access/common/heaptuple.c,v 1.111 2006/10/04 00:29:47 momjian Exp $
19+
* $PostgreSQL: pgsql/src/backend/access/common/heaptuple.c,v 1.112 2006/11/23 05:27:18 neilc Exp $
2020
*
2121
*-------------------------------------------------------------------------
2222
*/
@@ -631,6 +631,9 @@ heap_copytuple(HeapTuple tuple)
631631
*heap_copytuple_with_tuple
632632
*
633633
*copy a tuple into a caller-supplied HeapTuple management struct
634+
*
635+
* Note that after calling this function, the "dest" HeapTuple will not be
636+
* allocated as a single palloc() block (unlike with heap_copytuple()).
634637
* ----------------
635638
*/
636639
void

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp