From: Constantin Teodorescu <teo@flex.ro>
To: PostgreSQL Interfaces <pgsql-interfaces@postgresql.org>
Subject: GD global data array capabilities in pltcl
Date: Mon, 14 Oct 2002 19:12:10 +0300
Message-ID: <3DAAECDA.3080908@flex.ro> (raw)
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
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
Subject: Re: GD global data array capabilities in pltcl
In-Reply-To: <3DAAECDA.3080908@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