Talk:How to avoid overlapping intervals with PostgreSQL

From PostgreSQL wiki

(Difference between revisions)
Jump to: navigation, search
(New page: The concurrency problem here is the usual one; the code is trying to check for the presence of conflicting rows even though those rows may not yet be visible in the current session. ~~~~)
 
 
Line 1: Line 1:
 
The concurrency problem here is the usual one; the code is trying to check for the presence of conflicting rows even though those rows may not yet be visible in the current session.  [[User:Rhodiumtoad|Rhodiumtoad]] 01:55, 30 June 2010 (UTC)
 
The concurrency problem here is the usual one; the code is trying to check for the presence of conflicting rows even though those rows may not yet be visible in the current session.  [[User:Rhodiumtoad|Rhodiumtoad]] 01:55, 30 June 2010 (UTC)
 +
 +
In version 9.1 or later, concurrency problems could be avoided by using the serializable transaction isolation level.  (The triggers would need to check for that to be safe.)  In version 9.0 or later, though, a far better way to implement this is with exclusion constraints.  [[User:kgrittn|Kevin Grittner]]

Latest revision as of 15:11, 2 November 2011

The concurrency problem here is the usual one; the code is trying to check for the presence of conflicting rows even though those rows may not yet be visible in the current session. Rhodiumtoad 01:55, 30 June 2010 (UTC)

In version 9.1 or later, concurrency problems could be avoided by using the serializable transaction isolation level. (The triggers would need to check for that to be safe.) In version 9.0 or later, though, a far better way to implement this is with exclusion constraints. Kevin Grittner

Personal tools