Re: Protect a table against concurrent data changes while allowing to vacuum it - Mailing list pgsql-general

From Vlad Arkhipov
Subject Re: Protect a table against concurrent data changes while allowing to vacuum it
Date
Msg-id 576A6F02.4010805@dc.baikal.ru
Whole thread Raw
In response to Re: Protect a table against concurrent data changes while allowing to vacuum it  (Albe Laurenz <laurenz.albe@wien.gv.at>)
List 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.



pgsql-general by date:

Previous
From: Albe Laurenz
Date:
Subject: Re: Protect a table against concurrent data changes while allowing to vacuum it
Next
From: SDAG
Date:
Subject: pg_restore error-s after pg_dump