| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Christian Gonzalez <christian(dot)gonzalez(at)sigis(dot)com(dot)ve> |
| Cc: | 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:13:12 |
| Message-ID: | 603c8f070909021213o605fa483w81b1a18787337fee@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 2, 2009 at 11:29 AM, Christian
Gonzalez<christian(dot)gonzalez(at)sigis(dot)com(dot)ve> wrote:
> The point:
> There is some way to keep objects in [persisten] memory and then refer to
> these from c functions?. In the current version of pgRoute, each
> transaction load the graph in memory (using MemoryContext), this isn't a
> enterprise solution for routing program. Why I Wish is using a c function
> to load the graph in memory [persistent], something like:
Well note that whatever you allocate in TopMemoryContext (or wherever)
is going to be private to a single backend. If it's shared data, you
probably want to put it in a table, I would think...
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2009-09-02 19:17:23 | Re: c function: keep objects in memory for all session or all transaction |
| Previous Message | Robert Haas | 2009-09-02 19:10:53 | Re: remove flatfiles.c |