<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: tom-lane</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/tom-lane.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2008-07-07T14:08:19+00:00</updated><author><name>Simon Willison</name></author><entry><title>Quoting Tom Lane</title><link href="https://simonwillison.net/2008/Jul/7/postgres/#atom-tag" rel="alternate"/><published>2008-07-07T14:08:19+00:00</published><updated>2008-07-07T14:08:19+00:00</updated><id>https://simonwillison.net/2008/Jul/7/postgres/#atom-tag</id><summary type="html">
    &lt;blockquote cite="http://archives.postgresql.org/pgsql-hackers/2008-05/msg00913.php"&gt;&lt;p&gt;Historically the project policy has been to avoid putting replication into core PostgreSQL, so as to leave room for development of competing solutions [...] However, it is becoming clear that this policy is hindering acceptance of PostgreSQL to too great an extent, compared to the benefit it offers to the add-on replication projects.  Users who might consider PostgreSQL are choosing other database systems because our existing replication options are too complex to install and use for simple cases.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://archives.postgresql.org/pgsql-hackers/2008-05/msg00913.php"&gt;Tom Lane&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/databases"&gt;databases&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/postgresql"&gt;postgresql&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/replication"&gt;replication&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/tom-lane"&gt;tom-lane&lt;/a&gt;&lt;/p&gt;



</summary><category term="databases"/><category term="postgresql"/><category term="replication"/><category term="tom-lane"/></entry></feed>