Re: SET variable - Permission issues

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: SET variable - Permission issues
Дата
Msg-id CA+Tgmoa5dTVuyS7zBH3YtzVe_+iryMFvj7qStaEJLUA0NtSBng@mail.gmail.com
обсуждение исходный текст
Ответ на Re: SET variable - Permission issues  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: SET variable - Permission issues
Список pgsql-hackers
On Mon, Oct 10, 2011 at 2:38 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Any developer who can't think of six ways to DOS the server without
> changing those settings should be fired on the spot for incompetence.

No kidding.  But the point is that if the developer down the hall
maliciously destroys your database server, you can go through channels
and get him reprimanded or fired.  But if the developer down the hall
is a new hire who doesn't know beans about PostgreSQL and tries
setting work_mem to 10GB, well, oops, it was an accident.  And then
another developer gets hired three weeks later and does the same
thing.  And then three months later somebody does it again.  After a
while people no longer remember that in each case it was  a developer
to blame.  What they remember is that the DBA let the server go down
three times.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: ALTER EXTENSION .. ADD/DROP weirdness
Следующее
От: Greg Sabino Mullane
Дата:
Сообщение: Overhead cost of Serializable Snapshot Isolation