Re: advisory locks and permissions

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: advisory locks and permissions
Дата
Msg-id 200609210317.k8L3HqZ13438@momjian.us
обсуждение исходный текст
Ответ на Re: advisory locks and permissions  (Josh Berkus <josh@agliodbs.com>)
Ответы Re: advisory locks and permissions  (Jeremy Drake <pgsql@jdrake.com>)
Re: advisory locks and permissions  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Doesn't creating many temp tables in a transaction do the same thing?

---------------------------------------------------------------------------

Josh Berkus wrote:
> All,
> 
> > I vote for locking down to superuser access (lets be frank here: I
> > would estimate 90%+ database installatons run with the application as
> > root) so we are not losing much.
> 
> Not in my experience.   Note that making them superuser-only pretty much puts 
> them out of the hands of hosted applications.
> 
> How simple would it be to limit the number of advisory locks available to a 
> single request?  That would at least make the DOS non-trivial.  Or to put in 
> a handle (GUC?) that allows turning advisory locks off?
> 
> Hmmm ... I'll bet I could come up with other ways to use generate_series in a 
> DOS, even without advisory locks ...
> 
> -- 
> Josh Berkus
> PostgreSQL @ Sun
> San Francisco
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend

--  Bruce Momjian   bruce@momjian.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


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

Предыдущее
От: Josh Berkus
Дата:
Сообщение: Re: advisory locks and permissions
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: Release Notes: Major Changes in 8.2