From: Constantin Teodorescu <teo@flex.ro>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Nigel J. Andrews <nandrews@investsystems.co.uk>
Cc: PostgreSQL Interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: GD global data array capabilities in pltcl
Date: Tue, 15 Oct 2002 08:26:15 +0300
Message-ID: <3DABA6F7.5010607@flex.ro> (raw)
References: <Pine.LNX.4.21.0210141716470.584-100000@ponder.fairway2k.co.uk>
<17247.1034616537@sss.pgh.pa.us>
Tom Lane wrote:
>"Nigel J. Andrews" <nandrews@investsystems.co.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: teo@flex.ro, tgl@sss.pgh.pa.us, nandrews@investsystems.co.uk
Subject: Re: GD global data array capabilities in pltcl
In-Reply-To: <3DABA6F7.5010607@flex.ro>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox