A Hairy PostgreSQL Incident | Ardent Performance Computing
It was 5:17pm today, just as I was wrapping up work for the day, and my manager pinged me with the following chat: : Hi Jeremy – we have a ticket – esc…
postgres-ai/database-lab-engine: Thin PostgreSQL clones. DLE provides blazing-fast database cloning to build powerful development, test, QA, staging environments. Follow to stay updated.
DBLab enables 🖖 database branching and ⚡️ thin cloning for any Postgres database and empowers DB testing in CI/CD. This optimizes database-related costs while improving time-to-market and software ...
fatkodima/online_migrations: Catch unsafe PostgreSQL (MySQL soon) migrations in development and run them easier (helpers for table/column renaming, changing column type, adding columns with default, background migrations, etc) in production.
Catch unsafe PostgreSQL migrations in development and run them easier in production (code helpers for table/column renaming, changing column type, adding columns with default, background migrations...
Five Easy to Miss PostgreSQL Query Performance Bottlenecks
PostgreSQL query planner is full of surprises, so a common-sense approach to writing performant queries is sometimes misleading. In this blog post, I'll describe examples of optimizing seemingly obvious queries with the help of EXPLAIN ANALYZE and Postgres metadata analysis.
Progress bar for Postgres queries – let's dive deeper | Database Lab · Instant clones of PostgreSQL databases · Postgres.ai
Recently, I have read a nice post titled "Query Progress Bar", by Brian Davis. It describes an interesting approach to observing the progress of slow query execution. At some point, the author mentions: > Don't use this in prod. And I agree. The article discusses long-running queries such as SELECTs, UPDATEs, DELETEs, and quite "invasive" methods of progress monitoring. In an OLTP production scenario, in most cases, we should try to limit the duration of such queries, setting statement_timeout to a very low value – such as 30 or even 15 seconds. Let's dive deeper into the topic of query progress monitoring, and discuss various types of queries, how to monitor their progress, considering production and non-production environments separately. Continue reading...
PG Phriday: Defining High Availability in a Postgres World
What does High Availability actually mean when we’re discussing Postgres clusters? High Availability Architect, Shaun Thomas, explores answers to this question in this week's installment of PGPhriday.
The Fastest Way To Load Data Into Postgres With Ruby on Rails
We are looking at 4 methods: Insert One Record at a Time, Bulk Inserts with Active Record Import, PostgreSQL Copy with Activerecord-copy, Using Background Jobs.