Re: Protect a table against concurrent data changes while allowing to vacuum it

From: Vlad Arkhipov <arhipov(at)dc(dot)baikal(dot)ru>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Protect a table against concurrent data changes while allowing to vacuum it
Date: 2016-06-22 10:57:06
Message-ID: 576A6F02.4010805@dc.baikal.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

That is why I need to lock the table before. The transactions are
running at the READ COMMITTED isolation level.

On 06/22/2016 06:49 PM, Albe Laurenz wrote:
> But be warned that this will only work if all transactions involved use
> the isolation level SERIALIZABLE.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message SDAG 2016-06-22 11:00:16 pg_restore error-s after pg_dump
Previous Message Albe Laurenz 2016-06-22 10:49:13 Re: Protect a table against concurrent data changes while allowing to vacuum it