LWN: Comments on "Core team statement on replication in PostgreSQL" https://lwn.net/Articles/284338/ This is a special feed containing comments posted to the individual LWN article titled "Core team statement on replication in PostgreSQL". en-us Thu, 25 Sep 2025 01:40:02 +0000 Thu, 25 Sep 2025 01:40:02 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net Core team statement on replication in PostgreSQL https://lwn.net/Articles/285966/ https://lwn.net/Articles/285966/ Cyberax <div class="FormattedComment"><pre> Nope. This is bad news. The PostgreSQL team STILL can't figure out that we need REAL replication for critical systems. Asynchronous replication IS NOT suitable for high-availability systems (cue: the word "asynchronous"). And in any case Slony is already VERY easy to install (copy a module and edit PostgreSQL config). In comparison, all synchronous replication systems require patching PostgreSQL source. </pre></div> Thu, 12 Jun 2008 23:47:22 +0000 Core team statement on replication in PostgreSQL https://lwn.net/Articles/285220/ https://lwn.net/Articles/285220/ szidikm <div class="FormattedComment"><pre> This is great news. </pre></div> Fri, 06 Jun 2008 14:33:18 +0000 Core team statement on replication in PostgreSQL https://lwn.net/Articles/285115/ https://lwn.net/Articles/285115/ dmag <div class="FormattedComment"><pre> Yay. Simple things should be simple. Replication is a good first step. It doesn't solve every problem, but it's useful for scaling and fail-over. Cleaning up the simple stuff will let people move on to the complex stuff. Currently, real database High Availability is extremely messy. If you want your cluster to be ACID, there are no simple answers, only trade-offs. <a href="http://spyced.blogspot.com/2006/04/database-replication.html">http://spyced.blogspot.com/2006/04/database-replication.html</a> </pre></div> Thu, 05 Jun 2008 15:47:16 +0000