| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Andreas Kretschmer <akretschmer(at)spamfence(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: disallow SET WORK_MEM |
| Date: | 2011-12-05 20:00:57 |
| Message-ID: | 2911.1323115257@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Andreas Kretschmer wrote:
>> is it possible to disallow "set work_mem to ..." for regular
>> (non-superuser) users?
> We have discussed it and might offer that ability some day, but
> currently there is no way to do that. There are so many ways to mess
> things up with a bad query that we are unclear if restricting work_mem
> is really helpful.
Preventing people from setting an appropriate work_mem might well create
more denial-of-service problems than it prevents.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | C. Mundi | 2011-12-05 21:34:00 | Re: High-Concurrency GiST in postgreSQL |
| Previous Message | Andy Colson | 2011-12-05 19:26:54 | Re: High-Concurrency GiST in postgreSQL |