From: | wieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | wieck(at)debis(dot)com |
Cc: | pgman(at)candle(dot)pha(dot)pa(dot)us, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] LONG |
Date: | 1999-12-13 06:46:01 |
Message-ID: | m11xPFB-0003kGC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Mount | 1999-12-13 08:07:20 | RE: [HACKERS] 6.6 release |
Previous Message | Jan Wieck | 1999-12-13 06:34:30 | Re: [HACKERS] update_pg_pwd |