Learnings

<p>It's Time to Start Paying Attention to Vector Databases: </p>

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

<p>django-add-default-value: This django Migration Operation can be used to transfer a Fields default value to the database scheme. </p>

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

<p>Django extension to allow working with 'clusters' of models as a single unit, independently of the database: </p>

<p>Hosting SQLite databases on static pages </p>

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

<p>Log all queries of Postgres on docker-compose: </p>

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

<p>The trouble with transaction atomic: </p>

<p>The cost of a join and some benchmarks </p>

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

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

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

<p>How to Modernize a Django Index Definition with Zero Downtime: </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>Django application providing queryset sealing capability to force appropriate usage of <code>only()</code>/<code>defer()</code> and <br><code>select_related()</code>/<br><code>prefetch_related()</code></p>

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

<p>Lessons learned scaling PostgreSQL database to 1.2bn records/month: </p>

<p>PostgreSQL Configuration for Humans: </p>

<p>Getting The Most Out Of Your PostgreSQL Indexes: </p>

<p>Select first row in each GROUP BY group? </p>

<p>Is a Postgres long-running query aborted if the connection is lost/broken? </p>