| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk> |
| Cc: | Constantin Teodorescu <teo(at)flex(dot)ro>, PostgreSQL Interfaces <pgsql-interfaces(at)postgresql(dot)org> |
| Subject: | Re: GD global data array capabilities in pltcl |
| Date: | 2002-10-14 17:28:57 |
| Message-ID: | 17247.1034616537@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
"Nigel J. Andrews" <nandrews(at)investsystems(dot)co(dot)uk> writes:
> so I would say it's not accessable from other functions within the same
> backend. I doubt very much that this data is database wide I can only see it
> being backend specific.
It's definitely backend-local. I imagine you could access another
procedure's GD if you could determine its name (it's built from the
pg_proc OID, I think). However, if you want to share global data across
pltcl functions in the same backend session, you shouldn't bother with
GD at all: just create named global Tcl variables. All pltcl functions
in a backend run in the same interpreter, so they can trivially access
global variables.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jmelesky | 2002-10-14 17:47:47 | DBD::Pg now without maintainer |
| Previous Message | Nigel J. Andrews | 2002-10-14 16:20:40 | Re: GD global data array capabilities in pltcl |