It's probably a pretty basic question explained in some document I haven't seen
but...if I do something like a CreateTupleDescCopy() how do I know my memory
context owns everything allocated without following the code all the way
through until it returns to me?
--
Nigel J. Andrews
On Tue, 3 Sep 2002, Nigel J. Andrews wrote:
It's probably a pretty basic question explained in some document I haven't seen
but...if I do something like a CreateTupleDescCopy() how do I know my memory
context owns everything allocated without following the code all the way
through until
On Tue, Sep 03, 2002 at 12:28:37PM +0100, Nigel J. Andrews wrote:
It's probably a pretty basic question explained in some document I haven't seen
but...if I do something like a CreateTupleDescCopy() how do I know my memory
context owns everything allocated without following the code all
On Tue, 3 Sep 2002, Karel Zak wrote:
On Tue, Sep 03, 2002 at 12:28:37PM +0100, Nigel J. Andrews wrote:
It's probably a pretty basic question explained in some document I haven't seen
but...if I do something like a CreateTupleDescCopy() how do I know my memory
context owns everything
Nigel J. Andrews [EMAIL PROTECTED] writes:
It's probably a pretty basic question explained in some document I
haven't seen but...if I do something like a CreateTupleDescCopy() how
do I know my memory context owns everything allocated without
following the code all the way through until it
Maybe when this thread is over, some parts of it can be
added to the dev. FAQ?
-s
On Tue, 3 Sep 2002, Karel Zak wrote:
Date: Tue, 3 Sep 2002 13:52:09 +0200
From: Karel Zak [EMAIL PROTECTED]
To: Nigel J. Andrews [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [HACKERS] Memory
