| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-patches(at)postgresql(dot)org, Petr Jelinek <pjmodos(at)parba(dot)cz>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Subject: | Re: per user/database connections limit again |
| Date: | 2005-08-01 14:19:06 |
| Message-ID: | 2629.1122905946@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Peter Eisentraut wrote:
>> Would this not work in the context of the general user-specific ALTER USER ...
>> SET something = something?
> No because it isn't a GUC variable, it is per-user/db value. We could
> have used that syntax, but it might confuse people.
Yeah --- casting it as a GUC would create issues like "what is the
global default?". I think treating it as a hard-wired feature is fine.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2005-08-01 14:21:21 | Re: [HACKERS] For review: Server instrumentation patch |
| Previous Message | Bruce Momjian | 2005-08-01 14:13:18 | Re: per user/database connections limit again |