From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Christian Gonzalez <christian(dot)gonzalez(at)sigis(dot)com(dot)ve>, 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:17:23 |
Message-ID: | 4A9EC4C3.8090106@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2009-09-02 19:30:26 | Re: remove flatfiles.c |
Previous Message | Robert Haas | 2009-09-02 19:13:12 | Re: c function: keep objects in memory for all session or all transaction |