GD global data array capabilities in pltcl

From: Constantin Teodorescu <teo(at)flex(dot)ro>
To: PostgreSQL Interfaces <pgsql-interfaces(at)postgresql(dot)org>
Subject: GD global data array capabilities in pltcl
Date: 2002-10-14 16:12:10
Message-ID: 3DAAECDA.3080908@flex.ro
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

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

Responses

Browse pgsql-interfaces by date

  From Date Subject
Next Message Nigel J. Andrews 2002-10-14 16:20:40 Re: GD global data array capabilities in pltcl
Previous Message Constantin Teodorescu 2002-10-14 14:50:45 Re: What's wrong in this pltcl function ?