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

[Vlad Arkhipov <arhipov@xxxxxxxxxxxx>]

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.



--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general