# postgresql clusters PostgreSQL database clusters are collections of databases managed by a single running database server instance and stored in a data directory. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Kubernetes disaster recovery: Guidance from three reproducible failure scenarios DevFeed: [Kubernetes disaster recovery: Guidance from three reproducible failure scenarios]() Original publisher: [Read original article]() Author: Saiyam Pathak, Saloni Narang | CNCF Ambassadors Published: 2026-09-10T11:37:00Z Content type: article Language: en Sources: [Cloud Native Computing Foundation]() Topics: [Kubernetes](), [data](), [GitOps](), [postgresql clusters]() Tags: [blog](), [data](), [disaster-recovery](), [git](), [kubernetes](), [postgresql]() ### AI overview Guidance for recovering stateful Kubernetes applications through three reproducible failure scenarios, focusing on backup validation, declared versus stored state, and multi-volume consistency. ### Source excerpt Scope This document describes three failure scenarios that separate having backups from being able to recover, and the guidance that follows from each. Every scenario is reproducible on a laptop from the lab repository above, and... ## Autobase 2.11 released DevFeed: [Autobase 2.11 released]() Original publisher: [Read original article]() Published: 2026-09-09T00:00:00Z Content type: release Language: en Sources: [PostgreSQL news]() Topics: [postgresql clusters](), [Database](), [releases](), [Ansible Roles](), [cloud-infrastructure]() Tags: [ansible](), [cloud](), [operations](), [postgresql](), [postgresql-clusters](), [release]() ### AI overview Autobase 2.11 adds Platform UI management for PostgreSQL cluster scaling, minor and major upgrades, backups, and point-in-time recovery. It also introduces Ansible playbooks for backup and recovery operations. ### Source excerpt Autobase 2.11 is an important milestone in the evolution of the platform. Two years ago, we started working on a broader goal: evolve the Autobase Console from a PostgreSQL deployment UI into a platform for managing the complete cluster lifecycle. With this release, the remaining major pieces of that roadmap are now in place - scaling, upgrades, backups, and point-in-time recovery can all be managed directly from the Platform UI. See the full details in the release notes. Highlights Scaling (read replicas) Scale PostgreSQL read capacity directly from the UI. Simply specify the desired number of cluster nodes, and Autobase will provision the additional replicas automatically using the existing cloud configuration. For cloud deployments, the required servers and related infrastructure resources are created automatically. You can also scale clusters running on your own bare-metal or virtual machines. Start with a single-node PostgreSQL cluster and add replicas later as your workload grows. Upgrades Autobase Platform now supports minor upgrades within the current PostgreSQL major version as well as major-version upgrade workflows. For minor upgrades, replicas are updated one at a time, followed by a switchover and upgrade of the former primary. Read traffic remains available throughout the process, while expected write downtime is only ~5-10 seconds. For in-place major upgrades, the expected downtime is typically ~30-60 seconds. A blue-green major upgrade workflow with near-zero downtime is planned for a future release. Backup & Restore (PITR) Backup and recovery management is now available directly in the Platform UI. Configure the backup method, storage, retention, and schedule, or create backups on demand. Restore options include: Latest: recover to the latest available state Point in time: restore to a specific date and time Specific backup: restore from a selected backup New Ansible playbooks Autobase 2.11 adds new Ansible playbooks for backup and recovery operatio ## Fix circular role dependencies before upgrading Amazon RDS and Amazon Aurora PostgreSQL DevFeed: [Fix circular role dependencies before upgrading Amazon RDS and Amazon Aurora PostgreSQL]() Original publisher: [Read original article]() Author: Ravi Teja Adabala Published: 2026-08-31T23:42:55Z Content type: article Language: en Sources: [AWS Database Blog]() Topics: [PostgreSQL](), [RDS for PostgreSQL](), [Amazon Aurora](), [Amazon RDS](), [SQL](), [postgresql clusters](), [Graphs]() Tags: [amazon-aurora](), [amazon-rds](), [database](), [how-to](), [intermediate-200](), [postgresql](), [rds-for-postgresql](), [sql](), [technical-how-to]() ### AI overview This article explains how circular PostgreSQL role dependencies can cause major version upgrades of Amazon RDS for PostgreSQL and Amazon Aurora PostgreSQL to stall or roll back when upgrading from PostgreSQL 14 or earlier to PostgreSQL 15 or later. It describes a diagnostic query and steps to resolve the dependencies before the upgrade. ### Source excerpt Circular role dependencies can stall or roll back a major version upgrade of Amazon RDS for PostgreSQL or Amazon Aurora PostgreSQL when you move from PostgreSQL 14 or earlier to 15 or later. Learn why this happens, how to detect it with a single pre-upgrade query, and how to clear it before you upgrade. ## Day to day PostgreSQL on Kubernetes: Resize, Scale, and Upgrade DevFeed: [Day to day PostgreSQL on Kubernetes: Resize, Scale, and Upgrade]() Original publisher: [Read original article]() Author: Hans-Jürgen Schönig Published: 2026-08-25T06:16:00Z Content type: tutorial Language: en Sources: [CYBERTEC PostgreSQL | Services & Support]() Topics: [Kubernetes](), [PostgreSQL](), [postgresql clusters]() Tags: [capacity](), [commands](), [declarative](), [github](), [how-to](), [kubectl](), [kubernetes](), [operations](), [patroni](), [pg-operator](), [postgresql](), [postgresql-on-cloud](), [pull-requests](), [rolling-update](), [scale](), [upgrade]() ### AI overview A tutorial demonstrates resizing, scaling, and minor version upgrades for PostgreSQL running on Kubernetes with the CYBERTEC PG Operator. Using end-to-end minikube tests, it shows declarative manifest changes, rolling updates, Patroni failover, and scaling while the cluster remains available. ### Source excerpt This blog is about the resizing, scaling PostgreSQL in Kubernetes. This blog helps you learn various operation related to operations of PostgreSQL in Kubernetes. The post Day to day PostgreSQL on Kubernetes: Resize, Scale, and Upgrade appeared first on CYBERTEC PostgreSQL | Services & Support. ## Scale pgvector with binary quantization on Amazon Aurora PostgreSQL DevFeed: [Scale pgvector with binary quantization on Amazon Aurora PostgreSQL]() Original publisher: [Read original article]() Author: Steve Dille Published: 2026-08-18T16:37:22Z Content type: tutorial Language: en Sources: [AWS Database Blog]() Topics: [Amazon Aurora](), [PostgreSQL](), [quantization](), [AI search](), [Compression](), [Embeddings](), [Cache](), [Latency](), [datasets](), [configuration](), [postgresql clusters](), [Database]() Tags: [advanced-300](), [ai](), [amazon-aurora](), [cache](), [compression](), [datasets](), [embeddings](), [latency](), [postgresql](), [postgresql-compatible](), [quantization](), [rds-for-postgresql](), [search](), [technical-how-to](), [validation](), [vector]() ### AI overview This practical guide explains how to use binary quantization with reranking in pgvector to scale HNSW vector search on Amazon Aurora PostgreSQL. It covers index-size reduction, performance and recall tradeoffs, sizing, validation, and suitable operating conditions for datasets ranging from 5 million to 100 million vectors. ### Source excerpt Learn how to use binary quantization with reranking (HNSW+BQ) in pgvector to scale vector search to hundreds of millions or billions of vectors on Amazon Aurora PostgreSQL, with practical guidance on index sizing, recall validation, and the scenarios where the approach works best. ## Highly Available PostgreSQL on Kubernetes in 10 Minutes DevFeed: [Highly Available PostgreSQL on Kubernetes in 10 Minutes]() Original publisher: [Read original article]() Author: Hans-Jürgen Schönig Published: 2026-08-18T05:07:31Z Content type: tutorial Language: en Sources: [CYBERTEC PostgreSQL | Services & Support]() Topics: [PostgreSQL](), [Kubernetes](), [postgresql clusters](), [Database](), [Replication]() Tags: [failover](), [health-checks](), [how-to](), [kubernetes](), [operator](), [patroni](), [pg-operator](), [postgresql](), [postgresql-on-cloud](), [replication](), [tutorial](), [yaml]() ### AI overview This tutorial demonstrates how to deploy a highly available PostgreSQL cluster on Kubernetes with the CYBERTEC PG Operator. Using a 14-line YAML configuration on minikube, it shows leader election, streaming replication, health checks, automatic failover, and read-only replica behavior. It also explains how anti-affinity must be disabled for the single-node minikube setup but should remain enabled on multi-node production clusters. ### Source excerpt This is a detailed blog post about PostgreSQL in Kubernetes, using PG Operator. The post Highly Available PostgreSQL on Kubernetes in 10 Minutes appeared first on CYBERTEC PostgreSQL | Services & Support. ## Poisoned Postgres connection pools DevFeed: [Poisoned Postgres connection pools]() Original publisher: [Read original article]() Author: Josh Brown Published: 2026-08-18T00:00:00Z Content type: article Language: en Sources: [Blog -- PlanetScale]() Topics: [Database](), [postgresql clusters](), [client](), [API]() Tags: [api](), [database](), [engineering](), [postgres]() ### AI overview The article explains how stale session state can poison Postgres connection pools, causing reused connections to remain read-only and trigger errors. It focuses on connection pooling, PgBouncer transaction mode, and the resulting effects on client queries and API routes. ### Source excerpt An engineer's worst nightmare is waking up to a seemingly read-only database with no clear issue in sight. Let's dig into why this happens, and how AI can help solve it. ## The dangers of Postgres subtransactions DevFeed: [The dangers of Postgres subtransactions]() Original publisher: [Read original article]() Author: Etienne Berube Published: 2026-08-11T00:00:00Z Content type: article Language: en Sources: [Blog -- PlanetScale]() Topics: [PostgreSQL](), [postgresql clusters](), [Database](), [Server](), [data]() Tags: [availability](), [data](), [database](), [engineering](), [postgres](), [postgresql](), [server]() ### AI overview Postgres subtransactions can reduce throughput across an entire PostgreSQL cluster and prevent newly added read replicas from accepting queries. The article explains how replicas replay the primary's WAL and determine when they can safely serve reads. ### Source excerpt Subtransactions can slow down your entire PostgreSQL server and break your high availability strategy by keeping new read replicas from accepting connections. ## Mastering PostgreSQL Configuration Management with CloudNativePG (CNPG) DevFeed: [Mastering PostgreSQL Configuration Management with CloudNativePG (CNPG)]() Original publisher: [Read original article]() Author: Wellingtone Luvonga Published: 2026-08-04T05:00:38Z Content type: tutorial Language: en Sources: [CYBERTEC PostgreSQL | Services & Support]() Topics: [configuration](), [PostgreSQL](), [postgresql clusters](), [Kubernetes](), [GitOps](), [YAML](), [kubectl]() Tags: [administration](), [cloudnativepg](), [configuration](), [configuration-management](), [gitops](), [how-to](), [kubectl](), [kubernetes](), [postgresql](), [replication](), [yaml]() ### AI overview This tutorial explains how CloudNativePG manages PostgreSQL configuration in Kubernetes. It contrasts imperative editing of configuration files with declarative management through Kubernetes YAML and shows how to define database parameters and pg_hba.conf rules in a CNPG cluster resource. ### Source excerpt This blog talks about Configuration Management in PostgreSQL with CNPG, with some great examples in a comprehensive way. The post Mastering PostgreSQL Configuration Management with CloudNativePG (CNPG) appeared first on CYBERTEC PostgreSQL | Services & Support. ## One Postgres cluster, many apps DevFeed: [One Postgres cluster, many apps]() Original publisher: [Read original article]() Author: Simeon Griggs Published: 2026-06-25T00:00:00Z Content type: tutorial Language: en Sources: [Blog -- PlanetScale]() Topics: [postgresql clusters](), [Database](), [App](), [Authorization]() Tags: [administration](), [apps](), [complexity](), [database](), [databases](), [engineering](), [postgres](), [side-projects]() ### AI overview This tutorial explains how multiple small applications can share a single PlanetScale Postgres cluster through separate logical databases. It covers clusters, branches, logical databases, roles, permissions, and the tradeoff between shared infrastructure for side projects and dedicated clusters for applications that need to scale. ### Source excerpt Yo, I heard you liked databases, so we put logical databases in your database cluster so you can database while you database ## Building High Availability PostgreSQL Clusters with Patroni and Other Integrated Approaches DevFeed: [Building High Availability PostgreSQL Clusters with Patroni and Other Integrated Approaches]() Original publisher: [Read original article]() Author: Agus Syafaat Published: 2026-05-21T07:20:00Z Content type: tutorial Language: en Sources: [SeveralNines]() Topics: [postgresql clusters](), [PostgreSQL](), [Availability](), [Replication](), [Resilience](), [Automation](), [configuration](), [Open Source]() Tags: [automation](), [availability](), [configuration](), [consensus](), [database](), [distributed](), [failover](), [ha](), [high-availability](), [open-source](), [patroni](), [postgresql](), [postgresql-clusters](), [recovery-repair](), [replication]() ### AI overview This article explains how to build highly available PostgreSQL clusters with Patroni and related tools. It describes Patroni's use of replication, distributed consensus, a distributed configuration store, leader election, health checks, and YAML configuration to support automated failover. It also discusses operational challenges and the possible use of ClusterControl in the workflow. ### Source excerpt In modern application stacks, downtime is a direct threat to business continuity, customer trust, and revenue. Regardless of whether it is an e-commerce platform, a fintech application, or a critical internal system, the expectation is 24/7 availability, underscoring the critical importance of High Availability (HA) and automated failover mechanisms within PostgreSQL clusters. HA ensures that [...] The post Building High Availability PostgreSQL Clusters with Patroni and Other Integrated Approaches appeared first on Severalnines. ## How Discord Automates ScyllaDB Clusters at Scale DevFeed: [How Discord Automates ScyllaDB Clusters at Scale]() Original publisher: [Read original article]() Author: Peter French Published: 2026-05-08T00:00:00Z Content type: article Language: en Sources: [Discord Blog]() Topics: [Database](), [postgresql clusters](), [Replication](), [Concurrency](), [configuration](), [Orchestration](), [Rust](), [YAML](), [Prometheus](), [API]() Tags: [concurrency](), [database](), [how-to](), [metrics](), [prometheus](), [replication](), [rust](), [scylladb](), [workflow](), [workflows]() ### AI overview Discord describes how it automated ScyllaDB cluster operations with a Scylla Control Plane built around tasks, workflows, and jobs. The system uses explicit condition checks against Scylla's API and Prometheus metrics, idempotent Rust tasks, and YAML-defined workflows with retries, parallelism, configuration, and runtime templating. ### Source excerpt You've been asked to stand up a brand-new database cluster, meaning a whole day of configuring dozens of nodes, validating replication, wiring up dual-write pipelines... what if this whole ordeal took less than two hours? This is how we got ourselves into this exact mess, and how we made our way out of it. ## Waiting for PostgreSQL 19 - Online enabling and disabling of data checksums DevFeed: [Waiting for PostgreSQL 19 - Online enabling and disabling of data checksums]() Original publisher: [Read original article]() Author: depesz Published: 2026-04-15T18:05:36Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [postgresql clusters](), [async](), [IO]() Tags: [async](), [background](), [background-work](), [checksums](), [data-checksum](), [io](), [pg19](), [postgresql](), [uncategorized](), [vacuum](), [waiting]() ### AI overview This article examines a PostgreSQL 19 patch that allows data checksums to be enabled or disabled while a cluster is running. The command is immediate, but rewriting every table and index occurs in the background and can require substantial I/O. The article also discusses cost-delay options for controlling the background worker. ### Source excerpt On 3rd of April 2026, Daniel Gustafsson committed patch: Online enabling and disabling of data checksums This allows data checksums to be enabled, or disabled, in a running cluster without restricting access to the cluster during processing. Data checksums could prior to this only be enabled during initdb or when the cluster is ... Continue reading "Waiting for PostgreSQL 19 - Online enabling and disabling of data checksums" ## Waiting for PostgreSQL 19 - Introduce the REPACK command DevFeed: [Waiting for PostgreSQL 19 - Introduce the REPACK command]() Original publisher: [Read original article]() Author: depesz Published: 2026-03-19T18:07:59Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [postgresql clusters]() Tags: [analyze](), [bloat](), [command](), [indexes](), [locking](), [maintenance](), [pg-repack](), [pg19](), [planner](), [postgresql](), [repack](), [uncategorized](), [vacuum](), [waiting]() ### AI overview The article examines PostgreSQL 19's proposed built-in REPACK command, which combines functionality associated with VACUUM FULL and CLUSTER. It demonstrates reclaiming space and reordering a table, discusses locking because concurrent operation is not yet supported, and introduces the pg_stat_progress_repack progress view and available command forms. ### Source excerpt On 10th of March 2026, Álvaro Herrera committed patch: Introduce the REPACK command REPACK absorbs the functionality of VACUUM FULL and CLUSTER in a single command. Because this functionality is completely different from regular VACUUM, having it separate from VACUUM makes it easier for users to understand; as for CLUSTER, the term is heavily ... Continue reading "Waiting for PostgreSQL 19 - Introduce the REPACK command" ## Managed Databases Are Now Available in Laravel Forge DevFeed: [Managed Databases Are Now Available in Laravel Forge]() Original publisher: [Read original article]() Author: Laravel Team Published: 2026-03-17T15:48:55Z Content type: release Language: en Sources: [Laravel Blog]() Topics: [Laravel](), [postgresql clusters](), [Availability](), [Provisioning](), [Monitoring](), [Replication](), [Network](), [VPC]() Tags: [compute](), [databases](), [datacenter](), [high-availability](), [laravel](), [learn](), [memory](), [monitoring](), [network](), [postgres](), [replication](), [security](), [storage](), [vpc]() ### AI overview Laravel Forge now offers managed PostgreSQL clusters provisioned directly from its dashboard. The service handles patching, backups, replication, failover, and monitoring, with configurable compute, storage, region, networking, and high-availability options. ### Source excerpt Let Laravel Forge handle managed Postgres clusters for you with automated backups, PITR, high availability, and monitoring, all from your Forge dashboard. ## Creating Backup Strategies in Serverless Postgres with Laravel Cloud DevFeed: [Creating Backup Strategies in Serverless Postgres with Laravel Cloud]() Original publisher: [Read original article]() Author: Laravel Team Published: 2026-01-23T17:50:13Z Content type: tutorial Language: en Sources: [Laravel Blog]() Topics: [Laravel](), [postgresql clusters](), [Serverless](), [Cloud](), [MySQL]() Tags: [autoscaling](), [backup](), [cloud](), [laravel](), [postgres](), [production](), [real-time](), [reduce](), [retention](), [scale](), [storage]() ### AI overview This article explains how to create a cost-conscious backup strategy for Laravel Cloud's Serverless Postgres. It covers continuous backup logging, retention windows, point-in-time recovery, autoscaling, scale to zero, and database hibernation, with a comparison to Laravel MySQL for archived workloads. ### Source excerpt Looking to save on costs while protecting your data? Read our tips for setting up a dynamic backup strategy in Laravel Cloud. ## Optimizing Databases on Kubernetes Ep.1: Provisioning a Cluster and Configuring PostgreSQL on Kubernetes DevFeed: [Optimizing Databases on Kubernetes Ep.1: Provisioning a Cluster and Configuring PostgreSQL on Kubernetes]() Original publisher: [Read original article]() Published: 2024-12-09T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Kubernetes](), [PostgreSQL](), [Provisioning](), [CloudNativePG](), [postgresql clusters](), [Linode](), [Replication](), [hosting]() Tags: [backups](), [build-vs-buy-database-solutions](), [cloudnativepg](), [cloudnativepg-setup](), [clusters](), [cnpg-postgresql-operator](), [cost-efficient-kubernetes-clusters](), [cost-optimization](), [database-infrastructure-on-linode](), [database-optimization-on-kubernetes](), [efficient-storage-with-zfspv](), [high-availability-postgresql-kubernetes](), [kubernetes](), [kubernetes-for-databases](), [kubernetes-for-startups](), [linode](), [postgresql](), [postgresql-clusters](), [postgresql-clusters-on-kubernetes](), [postgresql-replication-on-k8s](), [production](), [production-ready-postgresql-on-k8s](), [provisioning](), [provisioning-kubernetes-clusters](), [rancher](), [rancher-local-path-persistent-volumes](), [reducing-hosting-costs-with-kubernetes](), [replication](), [scalable-databases-on-kubernetes](), [scalable-postgresql-deployments](), [self-hosted-databases-vs-managed-services](), [setting-up-postgresql-on-kubernetes]() ### AI overview This introductory video demonstrates how to provision a Kubernetes cluster on Linode and configure production-ready PostgreSQL clusters on Kubernetes using CloudNativePG, including replication and backups. It also discusses storage, cost control, and build-versus-buy trade-offs. ### Source excerpt Introduction: In this introductory episode, Jérôme Petazzoni walks through the critical steps of provisioning a Kubernetes cluster tailored for running databases like PostgreSQL. Leveraging his extensive experience, Jérôme demonstrates practical tools and techniques to establish a scalable, cost-efficient database infrastructure while laying the groundwork for future optimizations covered in this series. Provisioning Kubernetes Clusters: A step-by-step guide to creating a reliable cluster using Linode. Setting Up PostgreSQL with CNPG: Deploying production-ready PostgreSQL clusters with built-in replication and backups. ## Tutorial: Building a Highly Available PostgreSQL Cluster with etcd, Patroni, HAProxy, and keepalived DevFeed: [Tutorial: Building a Highly Available PostgreSQL Cluster with etcd, Patroni, HAProxy, and keepalived]() Original publisher: [Read original article]() Author: Techno Tim Published: 2024-12-07T13:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [postgresql clusters](), [PostgreSQL](), [Tutorial](), [Database]() Tags: [clustering](), [ha](), [patroni](), [postgres](), [postgresql](), [production](), [self-hosted](), [tutorial]() ### AI overview A tutorial for building a highly available and fault-tolerant PostgreSQL cluster with etcd, Patroni, HAProxy, and keepalived. It covers PostgreSQL node setup, certificate-based communication, etcd configuration, and cluster verification. ### Source excerpt Today is the day that you start running PostgresSQL in a cluster! In this tutorial we'll be setting up a production ready Postgres cluster that's highly available and fault tolerant using PostgreSQL, etcd, Patroni, HA Proxy, and keepalived. This resilient combination will ensure that you can always reach your database even when a node in the cluster goes down! 📺 Watch Video Nodes # ha pr... ## Why pg\_dump Is Useful for PostgreSQL Data Migration and Troubleshooting DevFeed: [Why pg\_dump Is Useful for PostgreSQL Data Migration and Troubleshooting]() Original publisher: [Read original article]() Author: Robert Haas (noreply@blogger.com) Published: 2024-11-01T15:56:00Z Content type: opinion Language: en Sources: [Robert Haas]() Topics: [PostgreSQL](), [postgresql clusters](), [Databases](), [cpu](), [floating-point]() Tags: [backup](), [backups](), [cpu](), [database](), [floating-point](), [pg-dump](), [postgresql](), [sql](), [version]() ### AI overview The article explains why pg_dump is useful beyond full-cluster backups. Its human-readable SQL output can support database migration, major-version changes, CPU architecture changes, and troubleshooting, although it may require manual modification and can incur performance costs or fail in some cases. ### Source excerpt I wrote a blog post a couple of weeks ago entitled Is pg_dump a Backup Tool?. In that post, I argued in the affirmative, but also said that it's probably shouldn't be your primary backup mechanism. For that, you probably shouldn't directly use anything that is included in PostgreSQL itself, but rather a well-maintained third-party backup tool such as barman or pgbackrest. But today, I want to talk a little more about why I believe that pg_dump is both amazingly useful for solving all kinds of PostgreSQL-related problems and also just a great piece of technology. Read more " ## Adopting Neon branching in CI/CD pipelines: a practical story by Shepherd DevFeed: [Adopting Neon branching in CI/CD pipelines: a practical story by Shepherd]() Original publisher: [Read original article]() Author: Carlota Soto Published: 2024-07-11T16:14:05Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [CI/CD](), [GitHub Actions](), [migration](), [SQLite](), [postgresql clusters](), [Serverless]() Tags: [case-studies](), [ci-cd](), [clusters](), [community](), [github](), [github-actions](), [migration](), [pipelines](), [scale](), [serverless](), [sqlite]() ### AI overview Shepherd adopted Neon's database branching to improve CI/CD testing for its insurance pricing engine, Alchemist. After migrating from SQLite to Postgres, the team began creating ephemeral branches through GitHub Actions, reducing the need for dedicated synchronized testing databases and lowering idle infrastructure costs. ### Source excerpt "Branching saves us both money and developer time. We no longer have to set up an actual testing database instance and make sure the data is always synced with production. We now spin up an ephemeral branch when we need to and then tear it down via the create/delete Github Action... ## Postgres Support Case Recap DevFeed: [Postgres Support Case Recap]() Original publisher: [Read original article]() Author: Daniel Price Published: 2024-01-31T18:32:32Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [postgresql clusters](), [Database](), [Processes](), [servers]() Tags: [community](), [database](), [databases](), [errors](), [memory](), [postgres](), [process](), [recap](), [sql](), [support]() ### AI overview This article explains the Postgres error that occurs when the maximum number of simultaneous database connections is reached and some slots remain reserved for superusers. It describes how high connection counts consume operating-system processes and memory, explains how Neon manages max_connections according to compute size and memory, and shows how to check the limit with SHOW max_connections. ### Source excerpt At Neon Support, we've noticed users occasionally encountering connection limit errors while connecting applications to their databases. Today, we're sharing insights from our support exchanges to help you understand and avoid this issue in your setup. Specifically, our users som... ## Postgres Woes on OSX with libicui18n.69.dylib DevFeed: [Postgres Woes on OSX with libicui18n.69.dylib]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-04-21T13:33:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Homebrew](), [PostgreSQL](), [postgresql clusters](), [upgrade]() Tags: [dependencies](), [errors](), [homebrew](), [osx](), [postgres](), [postgresql](), [upgrade]() ### AI overview A troubleshooting account of a PostgreSQL startup failure on macOS caused by a missing libicui18n.69.dylib library. Reinstalling icu4c with Homebrew led to PostgreSQL being upgraded and running locally again. ### Source excerpt Perhaps it is me but I've found that homebrew seems to give more errors and take longer than it used it. I just got hit with this error: /usr/local/opt/postgresql/bin/postgres -v dyld: Library not loaded: /usr/local/opt/icu4c/lib/libicui18n.69.dylib Referenced from: /usr/local/opt/postgresql/bin/postgres Reason: image not found Digging into the OSX postgres log here: tail -n 100 /usr/local/var/log/postgresql.log helped but didn't tell me what to do. An awful lot of googling didn't find me an answer but then I hit on: brew reinstall icu4c That churned for a bit but then declared a decisive victory: 🍺 /usr/local/Cellar/maxima/5.46.0: 2,842 files, 119.1MB ==> Running `brew cleanup maxima`... Removing: /usr/local/Cellar/maxima/5.45.1_4... (2,774 files, 118.4MB) Removing: /Users/sjohnson/Library/Caches/Homebrew/maxima--5.45.1_4... (38.3MB) ==> Upgrading postgresql 13.2_2 -> 14.2_1 ==> Installing dependencies for postgresql: krb5 ==> Installing postgresql dependency: krb5 ==> Pouring krb5--1.19.3.catalina.bottle.tar.gz 🍺 /usr/local/Cellar/krb5/1.19.3: 162 files, 5.2MB ==> Installing postgresql ==> Pouring postgresql--14.2_1.catalina.bottle.tar.gz ==> Caveats To migrate existing data from a previous major version of PostgreSQL run: brew postgresql-upgrade-database This formula has created a default database cluster with: initdb --locale=C -E UTF-8 /usr/local/var/postgres For more details, read: https://www.postgresql.org/docs/14/app-initdb.html To restart postgresql after an upgrade: brew services restart postgresql Or, if you don't want/need a background service you can just run: /usr/local/opt/postgresql/bin/postgres -D /usr/local/var/postgres ==> Summary 🍺 /usr/local/Cellar/postgresql/14.2_1: 3,305 files, 45.5MB ==> Running `brew cleanup postgresql`... Removing: /usr/local/Cellar/postgresql/13.2_2... (3,218 files, 42.6MB) Removing: /Users/sjohnson/Library/Caches/Homebrew/postgresql--13.2_2... (11.1MB) ==> Checking for dependents of upgraded formulae... ==> No broken dep ## When Postgres Won't Start DevFeed: [When Postgres Won't Start]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-09-12T11:05:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [PostgreSQL](), [upgrade](), [postgresql clusters]() Tags: [install](), [logs](), [postgres](), [postgresql](), [server](), [sysadmin](), [upgrade]() ### AI overview A PostgreSQL installation was upgraded from version 11 to 12.4 without upgrading its data directory, preventing the database server from starting. The article explains how to diagnose the incompatibility through PostgreSQL logs and lists commands used to resolve it. ### Source excerpt TLDR Somehow my postgres installation was upgraded. When postgres is upgraded its data is NOT upgraded. This means postgres won't start BUT it will be a silent failure; you can only confirm this via the logs. tail -n 10 /usr/local/var/log/postgres.log The Long Version I went through a situation the other day where I would start and stop postgres and the database would NEVER be available for connection. Here is the error that I kept getting: ❯ psql psql: error: could not connect to server: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/tmp/.s.PGSQL.5432"? This blog posts lists all the commands I used for reference and how I fixed it: brew services restart postgres brew services stop postgres brew services start postgres rm -f /usr/local/var/postgres/postmaster.pid brew uninstall postgresql brew install postgresql brew reinstall postgresql brew upgrade postgres ls -l /usr/local/var/postgres/postmaster.pid ls -l /usr/local/var/postgres/ tail -n 10 /usr/local/var/log/postgres.log brew postgresql-upgrade-database tail -n 10 /usr/local/var/log/postgres.log As is always the case with this type of low level issue, the answer is ALWAYS IN THE DAMN LOGS and it is always the near to last command you use that finds it. Here's what I found: ❯ tail -n 10 /usr/local/var/log/postgres.log 2020-09-10 16:17:49.566 EDT [85169] FATAL: database files are incompatible with server 2020-09-10 16:17:49.566 EDT [85169] DETAIL: The data directory was initialized by PostgreSQL version 11, which is not compatible with this version 12.4. 2020-09-10 16:17:59.589 EDT [85170] FATAL: database files are incompatible with server 2020-09-10 16:17:59.589 EDT [85170] DETAIL: The data directory was initialized by PostgreSQL version 11, which is not compatible with this version 12.4. 2020-09-10 16:18:09.617 EDT [85172] FATAL: database files are incompatible with server 2020-09-10 16:18:09.617 EDT [85172] DETAIL: The data ## What are PostgreSQL Templates? DevFeed: [What are PostgreSQL Templates?]() Original publisher: [Read original article]() Author: Angelico de los Reyes Published: 2020-07-09T07:00:00Z Content type: tutorial Language: en Sources: [Supabase Blog]() Topics: [PostgreSQL](), [Template](), [postgresql clusters](), [Databases]() Tags: [database](), [databases](), [postgresql](), [use-cases]() ### AI overview The article explains PostgreSQL's built-in template databases, template1 and template0, and how they affect newly created databases. It covers customizing template databases, creating and using a separate custom template for different use cases, and the connection limitations of this approach. It also recommends pg_dump when replicating a database while preserving active connections. ### Source excerpt What are PostgreSQL templates and what are they used for? [Next page]()