From: | "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com> |
---|---|
To: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Number of connections |
Date: | 2007-12-10 15:07:25 |
Message-ID: | 1A6E6D554222284AB25ABE3229A927621129A1@nrtexcus702.int.asurion.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
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).
Jon
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2007-12-10 15:11:49 | Re: Number of connections |
Previous Message | Dave Page | 2007-12-10 14:54:05 | Creating types |