Josh Berkus <[email protected]> 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
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
