Re: changing sort_mem on the fly?

From: Neil Conway <neilc(at)samurai(dot)com>
To: "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>
Cc: Michael Fuhr <mike(at)fuhr(dot)org>, Lonni J Friedman <netllama(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: changing sort_mem on the fly?
Date: 2005-01-28 06:34:26
Message-ID: 1106894066.3226.104.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-01-28 07:43:13 Re: changing sort_mem on the fly?
Previous Message Michael Fuhr 2005-01-28 05:34:27 Re: query variables