Issue 296 - Don't let locking block Postgres's autovacuum (9)

How LOCK TABLE Can Harm Your Database's Health — Frequent use of LOCK TABLE could harm your database when it conflicts with autovacuuming: “If you use LOCK on a table frequently, there is a good chance that autovacuum will never be able to successfully process that table.”

A Few Postgres Best Practices — Use BIGINT or UUID for primary keys, keep your credentials rotated, and use connection pooling.

Geolocation with Postgres — A look at the process of loading geolocation data into a Postgres database and then making queries to geolocate IPs against it.

7 Things To Watch Out For In Your PostgreSQL Deployment — Maximizing performance and establishing confident predictability of your PostgreSQL deployment.

PostGIS 2.5.2, 2.4.7, 2.3.9 Released — Relatively minor bug fix releases but the first to be able to compile against Proj 6 if you wish to use that.