Re: advisory locks and permissions

Поиск
Список
Период
Сортировка
От Kevin Brown
Тема Re: advisory locks and permissions
Дата
Msg-id 20060921234446.GH11514@filer
обсуждение исходный текст
Ответ на Re: advisory locks and permissions  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > Doesn't creating many temp tables in a transaction do the same thing?
> 
> True, but it's a tad harder/less likely that you'd accidentally cause
> a problem that way.

Then why not use a GUC (that only an administrator can set) to control
the maximum number of advisory locks a given backend can take at any
one time?  Then it becomes the DBA's problem (and solution) if someone
manages to run the database out of shared memory through this
mechanism.



-- 
Kevin Brown                          kevin@sysexperts.com


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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: pg_upgrade: downgradebility
Следующее
От: Jeff Frost
Дата:
Сообщение: Re: Cause of moving-target FSM space-needed reports