Re: changing sort_mem on the fly? - Mailing list pgsql-general

From Neil Conway
Subject Re: changing sort_mem on the fly?
Date
Msg-id 1106894066.3226.104.camel@localhost.localdomain
Whole thread Raw
In response to Re: changing sort_mem on the fly?  ("Jim C. Nasby" <decibel@decibel.org>)
Responses Re: changing sort_mem on the fly?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Thu, 2005-01-27 at 20:03 -0600, Jim C. Nasby wrote:
> Yes, there is a risk allowing ad-hoc settings; you can starve the
> machine for memory.

A malicious user who can execute SELECT queries can already consume an
arbitrary amount of memory -- say, by disabling GEQO and self-joining
pg_class to itself 50 times. I'm not sure that letting users modify
sort_mem/work_mem actually increases the risk from malicious users.
Restricting this parameter to superusers only would also be a hit to
usability.

-Neil



pgsql-general by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: query variables
Next
From: Tom Lane
Date:
Subject: Re: changing sort_mem on the fly?