Christopher
> You could use a 1 column/1 row table perhaps. Use some sort of
locking
> mechanism.
>
> Also, check out contrib/userlock
userlock is definitely the way to go for this type of problem.
The are really the only way to provide locking facilities that live
outside transactions.
You
At 09:40 PM 8/17/2005, Alan Stange wrote:
is there a simple way to limit the number of concurrent callers to a
stored proc?
The problem we have is about 50 clients come and perform the same
operation at nearly the same time. Typically, this query takes a
few seconds to run, but in the case
Hi Alan,
On Wed, 17 Aug 2005, Alan Stange wrote:
> Hello all,
>
> is there a simple way to limit the number of concurrent callers to a
> stored proc?
>
> The problem we have is about 50 clients come and perform the same
> operation at nearly the same time. Typically, this query takes a few
> sec
You could use a 1 column/1 row table perhaps. Use some sort of locking
mechanism.
Also, check out contrib/userlock
Chris
Alan Stange wrote:
Hello all,
is there a simple way to limit the number of concurrent callers to a
stored proc?
The problem we have is about 50 clients come and perfor
Hello all,
is there a simple way to limit the number of concurrent callers to a
stored proc?
The problem we have is about 50 clients come and perform the same
operation at nearly the same time. Typically, this query takes a few
seconds to run, but in the case of this thundering herd the que
