> -----Original Message-----
> From: Dave Page [mailto:dpage@postgresql.org]
> 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:
> > 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 executing.
> >
> > The second solution would require less code than the first one.
>
> And would make pgAdmin more or less useless for most people.
>
> > Additionally, this second solution could be a preference setting:
> > "Multithreaded Yes/No"
Having the above option would be overall more useful to the entire
community. For those that want to limit the connections, pick No. For
users that like the current number of connections spawned, leave it as Yes.
PL/SQL Developer by All Around has this same option. Toad by Quest Software
has this option too. Most database IDEs have some sort of way to configure
the number of connections created by the tool.
Jon
