Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 17D4B475E1F for ; Tue, 15 Oct 2002 01:26:14 -0400 (EDT) Received: from relay.flex.ro (ns.flex.ro [193.230.255.2]) by postgresql.org (Postfix) with ESMTP id 7A8D0475E1E for ; Tue, 15 Oct 2002 01:26:12 -0400 (EDT) Received: from flex.ro (teo.flex.ro [193.230.255.11]) by relay.flex.ro (Postfix) with ESMTP id 94DD923FFB; Tue, 15 Oct 2002 08:26:11 +0300 (EEST) Message-ID: <3DABA6F7.5010607@flex.ro> Date: Tue, 15 Oct 2002 08:26:15 +0300 From: Constantin Teodorescu User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: "Nigel J. Andrews" , PostgreSQL Interfaces Subject: Re: GD global data array capabilities in pltcl References: <17247.1034616537@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200210/46 X-Sequence-Number: 3208 Tom Lane wrote: >"Nigel J. Andrews" 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