Re: Memory Management in pqlib, Garbage Collection support

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Alexander Reichstadt <lxr(at)mac(dot)com>
Cc: 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 07:56:33
Message-ID: CABUevEyZw9bGkTJonEa37d2ZbXtWHvucOnpRXYRxa8rOwHuqog@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Albe Laurenz 2012-05-03 07:59:59 Re: Difference between speed of 2 functions: SQL+STABLE and PLPGSQL+EXECUTE
Previous Message John R Pierce 2012-05-03 07:56:05 Re: Uppercase to lowercase trigger?