Re: database-level lockdown

From: John R Pierce <pierce(at)hogranch(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: database-level lockdown
Date: 2015-07-04 18:10:35
Message-ID: 5598219B.8090307@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2015-07-04 18:23:01 Re: database-level lockdown
Previous Message Filipe Pina 2015-07-04 17:49:23 Re: database-level lockdown