Re: limiting connections per user/database

From: Alvaro Herrera <alvherre(at)surnet(dot)cl>
To: Petr Jelínek <pjmodos(at)parba(dot)cz>
Cc: Euler Taveira de Oliveira <eulerto(at)yahoo(dot)com(dot)br>, pgsql-patches(at)postgresql(dot)org
Subject: Re: limiting connections per user/database
Date: 2005-06-26 17:55:15
Message-ID: 20050626175515.GA7459@surnet.cl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

On Sun, Jun 26, 2005 at 07:46:32PM +0200, Petr Jelínek wrote:
> Euler Taveira de Oliveira wrote:
>
> >IIRC, people want the last one. We have more control if we can set it
> >per user or per database.
>
> Like I said, guc variables _can_ be set per user or per database if you
> use right context.

I don't think this approach is very user-friendly. I'd vote for the
catalog approach, I think.

> >Talking about pgstat, I think you can rely on
> >it 'cause it can be disabled. Could you describe the design you
> >intended to implement?
>
> I "can rely on it 'cause it can be disabled" - did you mean that I can't
> rely on it ?
> Well I am still not sure how I will implement it when I can't use
> pgstat. I think that I will have to use similar aproach which makes me sad.

Maybe you could make some checks against the shared array of PGPROCs
(procarray.c), for the per-database limit at least. Not sure about
per-user limit.

--
Alvaro Herrera (<alvherre[a]surnet.cl>)
"[PostgreSQL] is a great group; in my opinion it is THE best open source
development communities in existence anywhere." (Lamar Owen)

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Petr Jelínek 2005-06-26 18:52:55 Re: limiting connections per user/database
Previous Message Petr Jelínek 2005-06-26 17:46:32 Re: limiting connections per user/database