Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 707784762C3 for ; Mon, 14 Oct 2002 12:12:04 -0400 (EDT) Received: from relay.flex.ro (ns.flex.ro [193.230.255.2]) by postgresql.org (Postfix) with ESMTP id DC61E47626D for ; Mon, 14 Oct 2002 12:12:03 -0400 (EDT) Received: from flex.ro (teo.flex.ro [193.230.255.11]) by relay.flex.ro (Postfix) with ESMTP id 90282695A7 for ; Mon, 14 Oct 2002 19:12:08 +0300 (EEST) Message-ID: <3DAAECDA.3080908@flex.ro> Date: Mon, 14 Oct 2002 19:12:10 +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: PostgreSQL Interfaces Subject: GD global data array capabilities in pltcl Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200210/39 X-Sequence-Number: 3201 What would be the limitations of using the GD (global data) array in pltcl stored procedures ? I mean, if I'll keep there a big cache for a warehouse using set GD($itemId,quantity) $computedQuantity ... then elsewhere return $GS($itemId,quantity) would be a problem for let's say , 15000 articles? How would work the GD array in a heavy multi-user application? I presume that it is shared among any backend processes, isn't it? Are there some locking mechanisms? In other words, is the GD array appropriate to implement some caching features for a heavy used application in PostgreSQL? If not, are there any other sollutions (before going to EJB's and stuff) ? Thanks in advance, Constantin Teodorescu Braila, ROMANIA