Skip site navigation (1) Skip section navigation (2)

Re: Number of connections

From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
To: "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: Number of connections
Date: 2007-12-10 15:11:49
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgadmin-hackers
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 connection created.  So if a
> user wants to execute two concurrent queries, they actually have four
> database connections open.
> Wouldn't it be better to create a connection pool and only increment beyond
> one connection to the database when there are true concurrent requests?  I
> believe this is how M$ SQL Server handles this.  
> Alternatively, limiting the client to only one connection would be OK too
> and be less work than implementing a connection pool.  Maybe this could be a
> configuration setting. (Multi-thread yes/no).

Would be problematic at least for the Query Windows, because the SQL 
script might set session-variables, create temp tables etc.

   Heikki Linnakangas

In response to

pgadmin-hackers by date

Next:From: Roberts, JonDate: 2007-12-10 15:25:25
Subject: Re: Number of connections
Previous:From: Roberts, JonDate: 2007-12-10 15:07:25
Subject: Number of connections

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group