> -Original Message-
> From: Dave Page [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 10, 2007 10:11 AM
> To: Roberts, Jon
> Cc: pgadmin-hackers
> Subject: Re: [pgadmin-hackers] Number of connections
>
> Roberts, Jon wrote:
> > I mean this:
> &
Roberts, Jon wrote:
> I mean this:
> Solution 1: Manage a complicated connection pool like you described above.
> Solution 2: Only allow one connection to the database. A new query window
> will not create a new connection. The tool will not allow new queries to
> execute while another query is e
> -Original Message-
> From: Dave Page [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 10, 2007 9:42 AM
> To: Roberts, Jon
> Cc: pgadmin-hackers
> Subject: Re: [pgadmin-hackers] Number of connections
>
> Roberts, Jon wrote:
> > I would think far less co
Roberts, Jon wrote:
> I would think far less code would be needed if the tool could be configured
> to only use one connection.
How'd you figure that? You'd need to write the connection pooler, start
tracking connection states in far more detail than we do now, and
potentially have to start new
> -Original Message-
> From: Heikki Linnakangas [mailto:[EMAIL PROTECTED] On Behalf Of Heikki
> Linnakangas
> Sent: Monday, December 10, 2007 9:12 AM
> To: Roberts, Jon
> Cc: pgadmin-hackers
> Subject: Re: [pgadmin-hackers] Number of connections
>
> Roberts,
Roberts, Jon wrote:
I've noticed that when using pgAdmin, each user will have multiple
connections to the database. We actually observe three connections for each
user which seem to be:
1. pgAdmin UI
2. Maintenance database
3. Query Window
Then for each Query Window, there is another connect
I've noticed that when using pgAdmin, each user will have multiple
connections to the database. We actually observe three connections for each
user which seem to be:
1. pgAdmin UI
2. Maintenance database
3. Query Window
Then for each Query Window, there is another connection created. So if a
