Re: Automatically setting work_mem - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Automatically setting work_mem
Date
Msg-id 9732.1142626694@sss.pgh.pa.us
Whole thread Raw
In response to Re: Automatically setting work_mem  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Automatically setting work_mem
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> writes:
> Mind you, I'm also thinking that on enterprise installations with 
> multi-department use of the database, the fact that work_mem is 
> inalienably USERSET is also an allocation problem.   One user with a SET 
> command can blow all of your resource planning away.

One user with ability to enter arbitrary SQL commands can *always* blow
your resource planning away.  Blaming such things on work_mem is
seriously misguided.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Automatically setting work_mem
Next
From: Tom Lane
Date:
Subject: Re: Seperate command-line histories for seperate databases