From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Bill Studenmund <wrstuden(at)netbsd(dot)org> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Package support for Postgres |
Date: | 2001-10-20 09:27:34 |
Message-ID: | Pine.LNX.4.30.0110191909270.640-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bill Studenmund writes:
> > create function produce(text) returns text as '
> > GD["key"] = args[0]
> > ' language plpython;
> >
> > create function consume() returns text as '
> > return GD["key"]
> > ' language plpython;
> >
> > There is also a dictionary for private data.
>
> Private to what?
Private to the procedure, but saved across calls (during one session).
> Oh, by shared memory, do you mean SYSV Shared Memory (like how the
> backends talk) or just memory shared between routines? I ask as part of
> the idea with these variables is that they are backend-specific. So C
> routines actually should NOT used SYSV Shared Mem. :-)
Yes, you're right. Actually, sharing data across PostgreSQL C functions
is trivial because you can just use global variables in your dlopen
modules.
--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2001-10-20 09:27:52 | Re: Compiling on Solaris with Sun compiler |
Previous Message | Oleg Bartunov | 2001-10-20 08:26:08 | Re: Catalogs design question |