On Wed, 2004-09-15 at 19:51, Tom Lane wrote:
> "Katsaros Kwn/nos" <[EMAIL PROTECTED]> writes:
> > What I'm trying to do is to get the Query related to a select statement,
> > alter it and produce a new SPI_plan that will execute. To do so, I
> > retrieve the query from the _SPI_plan->qtlist, alter
"Katsaros Kwn/nos" <[EMAIL PROTECTED]> writes:
> On Wed, 2004-09-15 at 19:51, Tom Lane wrote:
>> You'd be well advised to be doing this sort of hackery in a build with
>> --enable-cassert. That turns on CLOBBER_FREED_MEMORY which makes
>> misuse of freed memory a whole lot more obvious.
> I did
On Wed, 2004-09-15 at 19:51, Tom Lane wrote:
> You'd be well advised to be doing this sort of hackery in a build with
> --enable-cassert. That turns on CLOBBER_FREED_MEMORY which makes
> misuse of freed memory a whole lot more obvious.
I did this but when I try do create a function the following
"Katsaros Kwn/nos" <[EMAIL PROTECTED]> writes:
> What I'm trying to do is to get the Query related to a select statement,
> alter it and produce a new SPI_plan that will execute. To do so, I
> retrieve the query from the _SPI_plan->qtlist, alter it (seems OK in
> nodeToString) and then use some SPI
Hi!
I posted the following message to the general list but no answer.Could
you please help?
I have some problems with the SPI memory management (at least I think
this is the problem).
What I'm trying to do is to get the Query related to a select statement,
alter it and produce a new SPI_plan that
