From: | Constantin Teodorescu <teo(at)flex(dot)ro> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>, PostgreSQL Interfaces <pgsql-interfaces(at)postgresql(dot)org> |
Subject: | Re: GD global data array capabilities in pltcl |
Date: | 2002-10-15 05:26:15 |
Message-ID: | 3DABA6F7.5010607@flex.ro |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
Tom Lane wrote:
>"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.
>
>
>
OK. Got that! Thanks a lot!
teo
From | Date | Subject | |
---|---|---|---|
Next Message | =?ISO-2022-JP?B?GyRCMiZJTBsoQg==?= | 2002-10-15 06:03:03 | backup problem |
Previous Message | t roussel | 2002-10-15 02:58:27 | problem mac osx |