From: | <cristian(at)clickdiario(dot)com> |
---|---|
To: | doug(at)mcnaught(dot)org, tjo(at)acm(dot)org |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: dynamic loading of .so |
Date: | 2005-10-16 23:54:21 |
Message-ID: | ozXzqVpq.1129506861.7416760.cristian@clickdiario.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
are there any way to make them global for all the instances?
On 10/14/2005, "Douglas McNaught" <doug(at)mcnaught(dot)org> wrote:
>TJ O'Donnell <tjo(at)acm(dot)org> writes:
>
>> I have begun to use some static variables in my c-language
>> functions to maintain state (3rd party licensing issues) during
>> the course of a session (postgres process, spawned by postmaster).
>> These are declared static outside the scope of any function.
>> (is global the correct term anymore?)
>> When I use dynamic loading of my .so,
>> each session is independent, with its own static variables.
>> Will the same be true if I were to load the .so once when
>> the database starts up? Or will there be just one set of
>> static variables for all sessions?
>
>Each backend process has its own memory space, so the variables will
>still be independent.
>
>-Doug
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: Don't 'kill -9' the postmaster
From | Date | Subject | |
---|---|---|---|
Next Message | Douglas McNaught | 2005-10-17 00:17:38 | Re: dynamic loading of .so |
Previous Message | talenat | 2005-10-16 23:54:13 | Collate problem |