On Wed, Jul 20, 2011 at 4:18 PM, Samuel Hwang <samuel@replicon.com> wrote:
> The real question is that why PostgreSQL behaves differently than
> other major DBMS. IMHO, doing checking at set operation boundary is
> more appropriate than at row boundary.
The real question is why anyone would actually perform that kind of
UPDATE. It doesn't really make much sense to increment a PK value.
PostgreSQL is good at supporting things people want and need, so
differences do exist in places that are fairly low priority.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
