Fix adaptation of gauge temporal validity The necessity to update validity implies the new value has to cascade through to referencing columns. Because measurements falling into the validity of a new version might have been already imported, a deadlock situation might occur with the CHECK constraint on gauge_measurements preventing an update of validity and the exclusion constraint on gauges preventing the insertion of a new version before the update. Thus, the exclusion constraint is now deferred and cannot longer be used with ON CONFLICT in the INSERT statement. Gauge measurements matching the validity of a new gauge version are now 'moved' to that new version before the validity of the old version is adapted.

532c8392048fe720bf31b7efb475591ab95a74ec v1-uat1
136aaa7f00af0b500c5c75f9fd9aabfc7fa526ee v1.1.0
724758455a4e44d25b096f00bcb353ceda0e0d57 v2-preview20190111
0059aa870a396e2112efae43f822c0c133454d7a v2
83f9a131dfb69f3ea1f430728a0831ccf96316d7 v2.1.0
83f9a131dfb69f3ea1f430728a0831ccf96316d7 v2.1.0
4d69b79e9df6e2b646ac60f75f6655bb3c64f6c6 v2.1.0