I think you might be able to accomplish this by setting up a pgpool
instance for just the read-only connections and limiting how many
connections are allowed there.
On Mar 26, 2007, at 3:20 PM, Saqib Awan wrote:
> Yes other than max_connections. I have a read-only user whose
> need to be limited to a number far less than max_connections.
> I cannot upgrade to latest version of the portgres since the newer
> ones has
> the support.
> -----Original Message-----
> From: Jim Nasby [mailto:decibel(at)decibel(dot)org]
> Sent: Saturday, March 24, 2007 2:26 PM
> To: Saqib Awan
> Cc: pgsql-general(at)postgresql(dot)org general
> Subject: Re: [GENERAL] Limiting user connnections on 7.4
> Dropping -hackers
> On Mar 22, 2007, at 4:23 AM, Saqib Awan wrote:
>> is there an existing mechanism to do user based connection
>> controls in
>> Postgres 7.4?
> Other than max_connections?
> Jim Nasby jim(at)nasby(dot)net
> EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
In response to
pgsql-hackers by date
|Next:||From: Josh Berkus||Date: 2007-04-30 17:04:25|
|Subject: Re: Feature freeze progress report|
|Previous:||From: Heikki Linnakangas||Date: 2007-04-30 15:46:29|
|Subject: Heap page diagnostic functions|
pgsql-general by date
|Next:||From: Oleg Bartunov||Date: 2007-04-30 16:45:44|
|Subject: Re: Stemming not working with tsearch2() function|
|Previous:||From: Craig A. James||Date: 2007-04-30 16:18:51|
|Subject: Re: Feature Request --- was: PostgreSQL Performance Tuning|