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

Re: TODO question and claim

From: Chris Humphries <chumphries(at)devis(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: TODO question and claim
Date: 2002-01-22 16:53:43
Message-ID: 3C4D9917.6060303@devis.com (view raw or flat)
Thread:
Lists: pgsql-hackers
sorry, i misunderstood what he said. since maxbackends is global,
would like something that isnt global, like relative to a db. here
is his messages:

--snip--

<DarcyB> maxbackends is GLOBAL, not specific to a DB and/or 
Authentication methood
<DarcyB> For example if you have a postgresinstall, with a maxbackends of 64
<chrish> authentication method?
<DarcyB> but that postmaster has 3 DB's in it.. (accounting, crm, demo)
<DarcyB> and you want to allow 32 connections to accounting 24 to crm 
and 8 to demo
<DarcyB> ....
<chrish> right, makes sence
<DarcyB> as per auth methood, I want to allow only 2 "remote" 
connections via SSL, and 16 via straight unix domain  and 14 via 
standatd TCP

--snip--

sorry for the communication error.

-chris


Tom Lane wrote:

> Chris Humphries <chumphries(at)devis(dot)com> writes:
> 
>>     First i would like to start off by coding a feature that DarcyB,
>>  nick from IRC, suggested as a starting point for me. A max connections
>>  settable limit.
>>
> 
> Uh, how is that different from MaxBackends?
> 
> 			regards, tom lane
> 



In response to

pgsql-hackers by date

Next:From: Keith G. MurphyDate: 2002-01-22 17:29:10
Subject: Re: [HACKERS] PostgreSQL Licence: GNU/GPL
Previous:From: Tom LaneDate: 2002-01-22 16:51:30
Subject: Re: RFD: schemas and different kinds of Postgres objects

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