Err. Methinks you are right.
I have a form that is generated from a query result set, and in each record, there is
a select widget which is, in turn, generated from a query result set. I can't run the
inner query until the outer query is exhausted, so I need 2 handles, I think!
Ian A. Harding
Programmer/Analyst II
Tacoma-Pierce County Health Department
(253) 798-3549
mailto: [EMAIL PROTECTED]
>>> [EMAIL PROTECTED] 09/05/01 02:17PM >>>
>From http://aolserver.com/docs/admin/con-ch3.htm#156726 :
ConnsPerThread
Default: 100
After the specified number of connections, a connection thread will exit.
This parameter is useful for working around memory leaks in Tcl code.
Which indicates that ConnsPerThread has nothing to do with DB stuff.
Is there a particular reason you need two db connections open at the same
time (to the same pool)?
Rusty
On Wed, 5 Sep 2001, Ian Harding wrote:
> Well, I tried uncommenting the connsperthread and setting it to 2 so I can have 2
>connections to the database within a thread. However, it does not seem to work.
>
> It looks like this...
>
> ns_param connsperthread 5 ;# Normally there's one conn per thread
>
> But I get this...
>
> [05/Sep/2001:14:08:54][19325.21][-conn2-] Error: dbinit: db handle limit exceeded:
>thread already owns 1 handle from pool 'pgpool'
> [05/Sep/2001:14:08:54][19325.21][-conn2-] Error: could not allocate 1 handle from
>pool "pgpool"
>
> I looked at the docs and could not find any leads. Any ideas?
>
> Ian A. Harding
> Programmer/Analyst II
> Tacoma-Pierce County Health Department
> (253) 798-3549
> mailto: [EMAIL PROTECTED]
>
------------------------------------------
Rusty Brooks : http://www.rustybrooks.org/
Spewing wisdom from every orifice
------------------------------------------
