user/sven/postgresql.git

Age	Commit message (Collapse)	Author
2015-05-11	Fix incorrect checking of deferred exclusion constraint after a HOT update.	Tom Lane
	If a row that potentially violates a deferred exclusion constraint is HOT-updated later in the same transaction, the exclusion constraint would be reported as violated when the check finally occurs, even if the row(s) the new row originally conflicted with have since been removed. This happened because the wrong TID was passed to check_exclusion_constraint(), causing the live HOT-updated row to be seen as a conflicting row rather than recognized as the row-under-test. Per bug #13148 from Evan Martin. It's been broken since exclusion constraints were invented, so back-patch to all supported branches.
2014-05-06	Remove tabs after spaces in C comments	Bruce Momjian
	This was not changed in HEAD, but will be done later as part of a pgindent run. Future pgindent runs will also do this. Report by Tom Lane Backpatch through all supported branches, but not HEAD
2011-01-01	Stamp copyrights for year 2011.	Bruce Momjian

2010-09-20	Remove cvs keywords from all files.	Magnus Hagander

2010-02-26	pgindent run for 9.0	Bruce Momjian

2010-01-02	Update copyright for the year 2010.	Bruce Momjian

2009-12-07	Add exclusion constraints, which generalize the concept of uniqueness to	Tom Lane
	support any indexable commutative operator, not just equality. Two rows violate the exclusion constraint if "row1.col OP row2.col" is TRUE for each of the columns in the constraint. Jeff Davis, reviewed by Robert Haas
2009-07-29	Support deferrable uniqueness constraints.	Tom Lane
	The current implementation fires an AFTER ROW trigger for each tuple that looks like it might be non-unique according to the index contents at the time of insertion. This works well as long as there aren't many conflicts, but won't scale to massive unique-key reassignments. Improving that case is a TODO item. Dean Rasheed