Following the link to the blog of the author I found a blog post titled “postgres cluster management system in GoCardless”<p><a href="http://www.interdb.jp/blog/pgsql/pg_pacemaker_01/" rel="nofollow">http://www.interdb.jp/blog/pgsql/pg_pacemaker_01/</a><p>Which in turn lead me to<p><a href="https://github.com/gocardless/our-postgresql-setup" rel="nofollow">https://github.com/gocardless/our-postgresql-setup</a><p>And in turn to a fifteen minute talk titled “Zero-downtime Postgres upgrades”<p><a href="https://www.youtube.com/watch?v=SAkNBiZzEX8" rel="nofollow">https://www.youtube.com/watch?v=SAkNBiZzEX8</a><p>Which was interesting and informative IMO.<p>After watching that one I was lead further via the YouTube suggested videos to a 45 minute talk titled “Tuning PostgreSQL for High Write Loads”<p><a href="https://www.youtube.com/watch?v=xrMbzHdPLKM" rel="nofollow">https://www.youtube.com/watch?v=xrMbzHdPLKM</a><p>Which I liked a lot as well.<p>I think anyone who came here because they are interested in the subject of the OP link might be interested in watching these videos.<p>Though disclaimer of course: These videos told me things I didn’t know about scaling PostgreSQL, because there is a lot I don’t know about that. But if you already know a lot about that then of course these videos might not be so interesting to you.
This is the thing I love about PostgreSQL, you can find out <i>everything</i> about the database. Oracle is ridiculous - they have something of the range of over a thousand hidden parameters, query tuning their CBO is somewhat of a black art and can change between point releases, and leads to articles like the following:<p><a href="http://www.dba-oracle.com/art_so_undoc_parms_p2.htm" rel="nofollow">http://www.dba-oracle.com/art_so_undoc_parms_p2.htm</a><p>PostgreSQL, however, has none of these limitations.
Reminded me that "Postgres is easy to install, administer, maintain, and use... with just a little bit of orientation. This is that orientation."<p>Christophe Pettus: PostgreSQL Proficiency for Python People - PyCon 2014.
<a href="https://www.youtube.com/watch?v=0uCxLCmzaG4" rel="nofollow">https://www.youtube.com/watch?v=0uCxLCmzaG4</a>
As a person who have started in SQL server, I really like the succinct clarity of Postgresql functions and its lightweight installation on the server. Thanks for sharing, this could really help me in the future.
Aside: do you still need to use a cache service when using Postgres? Our Django web app forgoes any caching because “Postgres is fast enough” and “has its own cache”.