Re: Memory Management in pqlib, Garbage Collection support

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Alexander Reichstadt <lxr(at)mac(dot)com>, Peter Bex <Peter(dot)Bex(at)xs4all(dot)nl>, John R Pierce <pierce(at)hogranch(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Memory Management in pqlib, Garbage Collection support
Date: 2012-05-03 08:32:47
Message-ID: CA+U5nMLEto+rOMonSAxuzjzL5n0GQ3Ha2WJLPRp68bw9Ea_2eQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, May 3, 2012 at 8:56 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> On Thu, May 3, 2012 at 9:39 AM, Alexander Reichstadt <lxr(at)mac(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alban Hertroys 2012-05-03 08:56:09 Re: Memory Management in pqlib, Garbage Collection support
Previous Message Peter Bex 2012-05-03 08:13:27 Re: Memory Management in pqlib, Garbage Collection support