Re: c function: keep objects in memory for all session or all transaction

From: Christian Gonzalez <christian(dot)gonzalez(at)sigis(dot)com(dot)ve>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: c function: keep objects in memory for all session or all transaction
Date: 2009-09-02 19:37:00
Message-ID: 4A9EC95C.4080108@sigis.com.ve
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ohh Thanks to all for your answers,
pgmemcache does exactly what I need, or how I need it, that is to
put my graph into a persistent memory for all transactions that have
permissions.

Thanks again,
Christian Gonzalez

El 02/09/09 14:47, Andrew Dunstan escribió:
>
>
> Peter Eisentraut wrote:
>> On ons, 2009-09-02 at 10:59 -0430, Christian Gonzalez wrote:
>>> Is posible to put persisten object in memory through postgresql c
>>> funtion?
>>
>> Well, the PL/Perl and PL/Python languages do some variants of this using
>> their GD and SD variables. So it's surely possible in C as well.
>> Memory contexts are the right keyword, but note that if you use
>> TopMemoryContext, you are pretty much just using malloc(). Maybe you
>> want to try prototyping your functionality in PL/Perl or PL/Python to
>> get it started.
>>
>
>
> But if you want something visible to all sessions, something like
> pg_memcache might be what you need. see
> <http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/~checkout~/pgmemcache/pgmemcache/README.pgmemcache?rev=1.11>
> for some details.
>
> cheers
>
> andrew
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-09-02 19:45:49 Re: remove flatfiles.c
Previous Message Greg Stark 2009-09-02 19:30:26 Re: remove flatfiles.c