Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

pgsql: Add a comment noting that heap_copytuple_with_tuple() results in - Mailing list pgsql-committers

From neilc@postgresql.org (Neil Conway)
Subject pgsql: Add a comment noting that heap_copytuple_with_tuple() results in
Date
Msg-id 20061123052719.C47B49FB1DD@postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Add a comment noting that heap_copytuple_with_tuple() results in a
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().

Modified Files:
--------------
    pgsql/src/backend/access/common:
        heaptuple.c (r1.111 -> r1.112)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/common/heaptuple.c.diff?r1=1.111&r2=1.112)

pgsql-committers by date:

Previous
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Update lock comments for concurrent index creation, analyze.
Next
From: neilc@postgresql.org (Neil Conway)
Date:
Subject: pgsql: More minor SGML improvements for xfunc.sgml, including making