Re: [HACKERS] LONG - Mailing list pgsql-hackers

From wieck@debis.com (Jan Wieck)
Subject Re: [HACKERS] LONG
Date
Msg-id m11xPFB-0003kGC@orion.SAPserv.Hamburg.dsh.de
Whole thread Raw
In response to Re: [HACKERS] LONG  (wieck@debis.com (Jan Wieck))
List pgsql-hackers
>     We  change  heap_formtuple(),  heap_copytuple()  etc.  not to
>     allocate the entire thing in one palloc(). Instead the  tuple
>     portion itself is allocated separately and the current memory
>     context remembered too  in  the  HeapTuple  struct  (this  is
>     required below).

Uhh,

    just  realized  that  the  usual  pfree(htup)  will  not work
    anymore. But shouldn't that already have been something  like
    heap_freetuple(htup)?


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#========================================= wieck@debis.com (Jan Wieck) #

pgsql-hackers by date:

Previous
From: wieck@debis.com (Jan Wieck)
Date:
Subject: Re: [HACKERS] update_pg_pwd
Next
From: Peter Mount
Date:
Subject: RE: [HACKERS] 6.6 release