Re: Memory Management in pqlib, Garbage Collection support - Mailing list pgsql-general

From Simon Riggs
Subject Re: Memory Management in pqlib, Garbage Collection support
Date
Msg-id CA+U5nMLEto+rOMonSAxuzjzL5n0GQ3Ha2WJLPRp68bw9Ea_2eQ@mail.gmail.com
Whole thread Raw
In response to Re: Memory Management in pqlib, Garbage Collection support  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Memory Management in pqlib, Garbage Collection support
List pgsql-general
On Thu, May 3, 2012 at 8:56 AM, Magnus Hagander <magnus@hagander.net> wrote:
> On Thu, May 3, 2012 at 9:39 AM, Alexander Reichstadt <lxr@mac.com> wrote:
>> Thanks, that's answering my question. In Objective-C as well as many other
>> languages there is the feature to turn on Garbage Collection. It's a
>> separate thread that scans memory for strong pointers, their source and
>> origin and "vacuums" memory so to not have any leaks. Anything unreferenced
>> and no longer needed is cleaned up automatically. There are some border
>> cases where GC can fail, but for most it works.
>
> libpq is a C library, not an objective-C library. So it clearly
> doesn't use an objective-c construct. If you are using some wrapper on
> top of libpq it might change things, but libpq itself has no knowledge
> of GC at all.

It would be nice to be able to garbage collect libpq programs
automatically though.

I think every time I read some libpq code I see an error.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-general by date:

Previous
From: Peter Bex
Date:
Subject: Re: Memory Management in pqlib, Garbage Collection support
Next
From: Alban Hertroys
Date:
Subject: Re: Memory Management in pqlib, Garbage Collection support