Re: database-level lockdown

Поиск
Список
Период
Сортировка
От John R Pierce
Тема Re: database-level lockdown
Дата
Msg-id 5598219B.8090307@hogranch.com
обсуждение исходный текст
Ответ на Re: database-level lockdown  (Filipe Pina <filipe.pina@impactzero.pt>)
Список pgsql-general
On 7/4/2015 10:49 AM, Filipe Pina wrote:
>
> Terminating all sessions will break every other transaction (except
> for the one doing it). Locking database will put all the other on hold.
> As we're talking about quick/instant operations on hold will have
> impact on performance but won't cause anything to abort..

you can't lock something thats already in use by a transaction as that
transaction already has locks on it.

better would be to design your workflow so it all can be done
transactionally and get away from this batch processing model.



--
john r pierce, recycling bits in santa cruz



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

Предыдущее
От: Filipe Pina
Дата:
Сообщение: Re: database-level lockdown
Следующее
От: Adrian Klaver
Дата:
Сообщение: Re: database-level lockdown