Re: C Function Memory Management

>
> One thing to know about it is that repalloc re-sizes the given chunk
> while keeping it in the same memory context it was originally allocated
> in (ie, CurrentMemoryContext doesn't matter). This may not matter much
> if you're only dealing with allocations that just live as long as the
> current function call --- but if you're trying to preserve data across
> calls, it's critical to know.
>
> regards, tom lane

Thanks for this Tom, I'll keep that in mind for future functions.

In this particular implementation, it's not necessary to preserve the data
once the function is complete.

So out of curiosity, what would be your approach for data preservation
cross call?

Cheers

Martin
=============================================

Romax Technology Limited
Rutherford House
Nottingham Science & Technology Park
Nottingham,
NG7 2PZ
England

Telephone numbers:
+44 (0)115 951 88 00 (main)

For other office locations see:
http://www.romaxtech.com/Contact
=================================
===============
E-mail: info(at)romaxtech(dot)com
Website: www.romaxtech.com
=================================

================
Confidentiality Statement
This transmission is for the addressee only and contains information that
is confidential and privileged.
Unless you are the named addressee, or authorised to receive it on behalf
of the addressee
you may not copy or use it, or disclose it to anyone else.
If you have received this transmission in error please delete from your
system and contact the sender. Thank you for your cooperation.
=================================================