Re:Postgres high-availability cluster with auto-failover and...
by Jweb_Guru on Tuesday November 17, 2015 @03:43AM
(#10579882)
To discourage people from using something broken. You're talking about a database that waited until 2011 to add a SERIALIZABLE implementation because the existing solutions all sucked, and only did it then because of new research (SSI). They have zero qualms about keeping features out of the database, no matter how useful, if they can't be implemented well.
[ Parent
| on HN ]
Re:Postgres high-availability cluster with auto-failover and...
by notpeter on Tuesday November 17, 2015 @04:38AM
(#10580045)
Forget serializable, PostgreSQL 7.0 included functional ACID-safe transactions 5 years before MySQL but didn't include LEFT OUTER JOIN (http://www.postgresql.org/docs/7.1/static/release-7-1.html) . That was my first taste of "if you can't do it right, don't ship it."
Re:Postgres high-availability cluster with auto-failover and...
by aravindet on Tuesday November 17, 2015 @04:29AM
(#10580025)
> They have zero qualms about keeping features out of the database, no matter how useful, if they can't be implemented well.
Another example, INSERT ... ON CONFLICT UPDATE (UPSERT/MERGE) available just now in the 9.5 beta.