| From: | Euler Taveira de Oliveira <eulerto(at)yahoo(dot)com(dot)br> |
|---|---|
| To: | Petr Jelínek <pjmodos(at)parba(dot)cz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: limiting connections per user/database |
| Date: | 2005-06-26 12:41:00 |
| Message-ID: | 20050626124100.97977.qmail@web32704.mail.mud.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Hi Petr,
> One more thing, do you have more concerns about that max connection
> out
> of the fact it uses pgstat ?
> For example are guc variables ok for this or should it be new
> variable
> in pg_shadow & pg_database etc - I would like to rewrite it just once
> or
> twice not ten times.
>
IIRC, people want the last one. We have more control if we can set it
per user or per database. Talking about pgstat, I think you can rely on
it 'cause it can be disabled. Could you describe the design you
intended to implement?
Euler Taveira de Oliveira
euler[at]yahoo_com_br
__________________________________________________
Converse com seus amigos em tempo real com o Yahoo! Messenger
http://br.download.yahoo.com/messenger/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2005-06-26 12:49:38 | Re: Escape patch applied |
| Previous Message | Pavel Stehule | 2005-06-26 07:50:23 | ToDo: Allow PL/pgSQL EXECUTE query_var INTO record_var; |