Ian Campbell writes ("Re: [OSSTEST PATCH 2/2] Executive DB: Reduce strength of
DB locks"):
> On Fri, 2015-12-11 at 16:23 +0000, Ian Jackson wrote:
> > SET TRANSACTION ISOLATION LEVEL SERIALIZABLE;
> > not mean that the transactions are necessarily serialisable!
>
> ^does not?
Yes, thanks.
> > Preventing concurrent read access means that simple and urgent updates
> > can be unnecessarily delayed by long-running reader transactions in
> > the history reporters and archaelogists.
>
> archaeologists
Fixed.
> > So, reduce the lock mode from ACCESS EXCLUSIVE to ACCESS. This still
> > conflicts with all kinds of updates and prospective updates, but no
> > longer with SELECT:
> > http://www.postgresql.org/docs/8.3/static/explicit-locking.html
> >
> > Signed-off-by: Ian Jackson <ian.jack...@eu.citrix.com>
>
> Acked-by: Ian Campbell <ian.campb...@citrix.com>
Thanks,
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
