Learnings

<p>Herding elephants: Lessons learned from sharding Postgres at Notion: </p>

<p>Cut Out the Middle Tier: Generating JSON Directly from Postgres - </p>

<p>Re-Introducing Hash Indexes in PostgreSQL </p>

<p>Zero downtime Postgres migration, done right </p>

<p>Scaling Relational SQL Databases: </p>

<p>postgres-checkup – automated PostgreSQL health checks: </p>

<p>pgbarman - taking an online hot backup of PostgreSQL is now as easy as ordering a good espresso coffee: </p>

<p>Hasura - Auto-generate GraphQL and REST APIs for your data: </p>

<p>Postgres - Transpose Rows to Columns: </p>

<p>Speeding up SQL queries by orders of magnitude using UNION: </p>

<p>Handling NULL values in Postgresql </p>

<p>A nice guide on how and when to tweak Postgres work_mem configuration variable </p>

<p>Heroku Postgres Database Tuning </p>

<p>Optimizing Postgres full text search in Django </p>

<p>Overview postgresql indexes </p>

<p>Quickly debugging Postgres problems: </p>

<p>How we used Postgres extended statistics to achieve a 3000x speedup: </p>

<p>Reading a Postgres EXPLAIN ANALYZE Query Plan: </p>

<p>Using Postgres Row-Level Security in Python and Django: </p>

<p>Is it worth it to run VACUUM on a table that only receives INSERTs? </p>

<p>Eight tips to relieve those Postgres headaches: </p>

<p>Faster Performance with Unlogged Tables in PostgreSQL: </p>

<p>When using psycopg2's ThreadedConnectionPool, an additional sempahore is needed to avoid "connection pool exhausted" errors: </p>

<p>PostgreSQL uses the search path to resolve object names. When we refer to a table using just its name, PostgreSQL searches for the table by using something called a <em>schema search path</em>, which is a list of schemas to look in. The default is <code>"$user", public</code>: </p>