| From: | Thomas Beutin <tyrone(at)laokoon(dot)IN-Berlin(dot)DE> |
|---|---|
| To: | Jose Antonio Martinez <lfbbes(at)yahoo(dot)es> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: max connections |
| Date: | 2003-02-20 18:14:48 |
| Message-ID: | 20030220191448.B16069@laokoon.bug.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Feb 20, 2003 at 06:56:52PM +0100, Jose Antonio Martinez wrote:
> yes, i know that max_connections limit the number of
> connections to the postgresql server, but it is a
> global limit for all the databases which are in the
> server. I am looking for a way of configuring
> postgresql for limiting connections per database at a
> shared database server enviroment. In mysql it is easy
> becouse there are a parameter for it.
Oops... sorry. I think there is no way. Maybe Your connection
pool can do this?
So long,
-tb
> --- Thomas Beutin <tyrone(at)laokoon(dot)IN-Berlin(dot)DE>
> escribió: > On Thu, Feb 20, 2003 at 04:17:33PM +0100,
> Jose
> > Antonio Martinez wrote:
> > > how can i limit the number of concurrent
> > connections
> > > to the same database at a postgresql server (wich
> > > have several databases)?
> > >
> > > is there any easy way?
> > command line: "-N x"
> > config file: "max_connections = x"
> >
> > It's all explained in the very good documentation.
> >
> > So long,
> > -tb
--
Thomas Beutin tb(at)laokoon(dot)IN-Berlin(dot)DE
Beam me up, Scotty. There is no intelligent live down in Redmond.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Cave-Ayland | 2003-02-20 18:21:46 | Re: 7.3.1 takes long time to vacuum table? |
| Previous Message | Andrew Sullivan | 2003-02-20 18:11:17 | Re: what kind of upgrade path is this |