Re: Built-in connection pool - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Built-in connection pool
Date
Msg-id 4C287A340200002500032BED@gw.wicourts.gov
Whole thread Raw
In response to Built-in connection pool  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
I wrote:
> When preparing to deal with a new statement:
>  - acquire lockX
>  - if not a superuser
>  - and not in an active transaction
>  - and countX >= max_active_transactions
>  -   place current process at tail of waitX queue, and block
>  -   (lockX would be released while blocked)
>  - increment countX
>  - release lockX
There's a bug there already.  This should be better:- if not in an active transaction-   acquire lockX-   if not a
superuser-  and countX >= max_active_transactions-     place current process at tail of waitX queue, and block-
(lockXwould be released while blocked)-   increment countX-   release lockX
 
-Kevin


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: pg_dump's checkSeek() seems inadequate
Next
From: Mike Rylander
Date:
Subject: Re: Issue: Deprecation of the XML2 module 'xml_is_well_formed' function