PostgreSQL gets a DuckDB-flavored power-up for faster analytical queries without ever leaving Postgres. | Reading time: 6 min read

Flexible CSV processing for Postgres. Contribute to PostgREST/pg_csv development by creating an account on GitHub.

Secure PostgreSQL in hybrid environments with best practices for auth, encryption, RLS, and centralized management to reduce risk and ensure compliance.

Learn how to set up automated PostgreSQL backups in Docker using pg_dump, cron scheduling, compression, and retention policies. Includes production-ready scripts and best practices for containerized databases.

Discover why PostgreSQL restores slow on foreign keys and how COPY FREEZE or VACUUM ANALYZE can speed up large restores.

A PostgreSQL extension that provides infinite calendar functionality for recurring schedules with exceptions. - h4kbas/pgcalendar

Postgres creates an execution plan for how to retrieve the data you're asking for in a query. The execution plan is based in part on statistics from your data and indexes it has available. Just the right index and a bit of query tuning can have a huge payoff in performance gains that your users will notice.

A guide to schema import, archival policies, and automation

Using RLS can be cumbersome, because it's usually expected to rely on the user name. Could we use JWT to establish a 'trusted context'?

Set up 3-Node highly available PostgreSQL cluster. Contribute to stormatics/pg_cirrus development by creating an account on GitHub.

In this blog post, we’ll dive deep into why we chose to build DBOS durable workflow execution on the PostgreSQL DBMS.

Eliminating PostgreSQL catalog traversal overhead with local partition calculations for up to 20x faster hash partition queries.

Level up with JSONB by adding GIN indexes. Also review when not to use a GIN index and how to leverage expression indexes.

Funny and weird behavior with modern SSD devices, and how it impacts query execution.

Review key logging configurations in Postgres plus how to log key performance metrics.

In order to achieve High Availability (HA) in Postgres, we need to have at least one other standby replica that keeps up with the primary’s changes near-real-time. Using Postgres physical replication is the most common method to achieve this.

Replication slots in Postgres keep track of how far consumers have read a replication stream. After a restart, consumers—​either Postgres read replicas or external tools for change data capture (CDC), like Debezium—resume reading from the last confirmed log sequence number (LSN) of their replication slot. The slot prevents the database from disposing of required log segments, allowing safe resumption after downtime. In this post, we are going to take a look at why Postgres replication slots don’t have one but two LSN-related attributes: restart_lsn and confirmed_flush_lsn. Understanding the difference between the two is crucial for troubleshooting replication issues, optimizing WAL retention, and avoiding common pitfalls in production environments.

The pg_meminfo Postgres Extension. Contribute to bonesmoses/pg_meminfo development by creating an account on GitHub.

This article explores techniques for achieving near zero-downtime during PostgreSQL migrations and upgrades

In this post: why are Postgres connections with sslmode=require insecure? How does Neon ensure secure connections? And what needs to happen to make secure Postgres connections the norm?

An intuitive spreadsheet-like interface that lets users of all technical skill levels view, edit, query, and collaborate on Postgres data directly—100% open source and self hosted, with native Post...

Building the first truly self-driving PostgreSQL: zero downtime upgrades, AI-powered automation, and a roadmap to full database autonomy.

As an respectable unemployed person must do, I tried to make Postgres as slow as possible

Nithin Bekal's blog about programming - Ruby, Rails, Vim, Elixir.

A comprehensive guide to using pgroll for safe, reversible Postgres migrations

Boost PostgreSQL full-text search speed by 50x with simple optimizations. Use VectorChord-BM25 to accelerate and better BM25 ranking in postgres.

Supabase is the Postgres development platform providing all the backend features you need to build a product.

Native BM25 Ranking Index in PostgreSQL. Contribute to tensorchord/VectorChord-bm25 development by creating an account on GitHub.

Worried about sharing private information with LLMs? See how to build a fully local RAG application using PostgreSQL, Mistral, and Ollama.