# RDS for PostgreSQL

A managed Amazon RDS service for deploying and operating PostgreSQL databases, including upgrades, storage, replication, backups, and security.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Performance impact of excessive logging in Amazon Aurora PostgreSQL

DevFeed: [Performance impact of excessive logging in Amazon Aurora PostgreSQL](<https://devfeed.tech/articles/performance-impact-of-excessive-logging-in-amazon-aurora-postgresql-144312.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/performance-impact-of-excessive-logging-in-amazon-aurora-postgresql/>)

Author: Baji Shaik

Published: 2026-11-19T19:10:08Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>), [performance-engineering](<https://devfeed.tech/topics/performance-engineering.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>)

Tags: [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [audit-logging](<https://devfeed.tech/tags/audit-logging.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [bottleneck](<https://devfeed.tech/tags/bottleneck.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [logging](<https://devfeed.tech/tags/logging.md>), [performance](<https://devfeed.tech/tags/performance.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [throughput](<https://devfeed.tech/tags/throughput.md>)

### AI overview

In a pgbench test on Aurora PostgreSQL 17, verbose logging had little effect at 8 clients, but at 800 clients, logging every statement reduced throughput by about 10%; adding `pgaudit.log = ALL` cut whole-run throughput from 16,202 to 5,039 TPS. Sampling showed sessions mostly active on CPU rather than waiting on instrumented resources, and a 537 MB log file written in under a minute supported a bottleneck in log generation and writing. The article recommends checking `pg_settings`, correlating slow periods with `pg_stat_activity` wait events and RDS log-file sizes, and testing at production-like concurrency. For audit needs, it suggests narrowing logged statement classes or using `pgaudit.log_statement = off` to retain structured audit details while dropping embedded SQL text; it advises confirming the reduction on the workload.

### Source excerpt

Excessive database and audit logging can quietly become a performance bottleneck in Amazon Aurora and Amazon RDS for PostgreSQL. Using a reproducible pgbench example, this post shows when logging overhead is negligible and when it cuts throughput by about three times, how to spot it with wait events and log file evidence, and how to reduce it.

## pgSherpa: a free PostgreSQL monitoring companion for macOS

DevFeed: [pgSherpa: a free PostgreSQL monitoring companion for macOS](<https://devfeed.tech/articles/pgsherpa-a-free-postgresql-monitoring-companion-for-macos-141066.md>)

Original publisher: [Read original article](<https://www.postgresql.org/about/news/pgsherpa-a-free-postgresql-monitoring-companion-for-macos-3446/>)

Published: 2026-11-18T00:00:00Z

Content type: release

Language: en

Sources: [PostgreSQL news](<https://devfeed.tech/sources/postgresql-news.md>)

Topics: [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [macOS](<https://devfeed.tech/topics/macos.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>)

Tags: [app-store](<https://devfeed.tech/tags/app-store.md>), [apple-silicon](<https://devfeed.tech/tags/apple-silicon.md>), [companion](<https://devfeed.tech/tags/companion.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [free](<https://devfeed.tech/tags/free.md>), [intel](<https://devfeed.tech/tags/intel.md>), [keychain](<https://devfeed.tech/tags/keychain.md>), [locks](<https://devfeed.tech/tags/locks.md>), [macos](<https://devfeed.tech/tags/macos.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [pg-stat-statements](<https://devfeed.tech/tags/pg-stat-statements.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [replication](<https://devfeed.tech/tags/replication.md>), [screen](<https://devfeed.tech/tags/screen.md>), [server](<https://devfeed.tech/tags/server.md>), [servers](<https://devfeed.tech/tags/servers.md>), [statement](<https://devfeed.tech/tags/statement.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [transaction](<https://devfeed.tech/tags/transaction.md>), [write](<https://devfeed.tech/tags/write.md>)

### AI overview

pgSherpa is a free macOS desktop companion that polls PostgreSQL 12-18 servers and surfaces issues with explanatory text and supporting rows. It offers a SQL box with server-version-specific `\h` help, plus reports for activity, locks, query statistics, vacuum progress, indexes, and replication. Statements run in read-only transactions unless switched to write. Setup requires a role with `pg_monitor`; no server extension or agent is installed. The excerpt says credentials stay in the macOS Keychain and that the app has no account or telemetry. It supports macOS 12 or later on Apple silicon and Intel Macs.

### Source excerpt

CortexRidge has released pgSherpa, a free desktop companion for PostgreSQL on macOS, now available on the Mac App Store. pgSherpa sits in a corner of the screen and polls one or more PostgreSQL servers (PostgreSQL 12 to 18). When something needs attention it says so in a sentence, with the rows behind it: Health: lock-wait chains, long-running and idle-in-transaction sessions, replication lag and replication slots, vacuum and transaction ID wraparound, connection limits. Security: the server's version compared with the latest PostgreSQL minor release and the CVEs fixed since, plus configuration such as SSL, MD5 passwords and superuser count. Cloud: backups, failovers, maintenance windows and replicas for DigitalOcean Managed Databases, Supabase and Amazon RDS / Aurora PostgreSQL, read from the provider's API. SQL: a query box with PostgreSQL completion and \h syntax help for the server's own version. Every statement runs in a read-only transaction unless the user switches it to write. Reports: ready-made views of pg_stat_activity, pg_locks, pg_stat_statements, vacuum progress, indexes and replication. pgSherpa needs only a role with pg_monitor. It installs no extension and no agent on the server, and it has no account and no telemetry; passwords and keys stay in the macOS Keychain. It runs on macOS 12 or later, on Apple silicon and Intel Macs. Mac App Store: https://apps.apple.com/app/id6833955115 More information: https://cortexridge.com/

## PostgreSQL large objects: Best practices for Amazon Aurora and RDS

DevFeed: [PostgreSQL large objects: Best practices for Amazon Aurora and RDS](<https://devfeed.tech/articles/postgresql-large-objects-best-practices-for-amazon-aurora-and-rds-136897.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/postgresql-large-objects-best-practices-for-amazon-aurora-and-rds/>)

Author: Sachin Murkar

Published: 2026-11-16T23:46:00Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Insight for DBAs](<https://devfeed.tech/topics/insight-for-dbas.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [prevent](<https://devfeed.tech/tags/prevent.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [triggers](<https://devfeed.tech/tags/triggers.md>), [upgrades](<https://devfeed.tech/tags/upgrades.md>)

### AI overview

PostgreSQL large objects can hold values up to 4 TB and support efficient partial reads and updates, but they live outside application tables, so autovacuum does not remove unlinked objects. The article recommends monitoring their count and storage, checking reference columns against vacuumlo's scan criteria, and using dry-run mode before cleanup. vacuumlo recognizes columns named oid or lo, but misses other domains over oid and columns such as integer, bigint, text, or custom types; missed references can be permanently deleted as supposed orphans. lo_manage triggers can unlink objects on row updates or deletes, but do not run for DROP or TRUNCATE. High object counts can also increase OID allocation contention and complicate major upgrades through pg_dump/pg_restore memory use. The guidance includes reducing orphan counts, testing upgrades on a clone, and considering temporary instance scaling when counts remain high.

### Source excerpt

PostgreSQL large objects live outside your tables and are referenced only by an OID, so autovacuum never reclaims the orphans. This post shows how to monitor orphaned large objects on Amazon Aurora and Amazon RDS for PostgreSQL, run vacuumlo safely, set up lo_manage triggers, prevent OID exhaustion, and prepare for major version upgrades.

## Improve RDS Proxy multiplexing for PostgreSQL, Part 1: Common causes

DevFeed: [Improve RDS Proxy multiplexing for PostgreSQL, Part 1: Common causes](<https://devfeed.tech/articles/improve-rds-proxy-multiplexing-for-postgresql-part-1-common-causes-133437.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/improve-rds-proxy-multiplexing-for-postgresql-part-1-common-causes/>)

Author: Pavel Rabinovich

Published: 2026-11-13T21:08:09Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [fragmentation](<https://devfeed.tech/tags/fragmentation.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [multiplexing](<https://devfeed.tech/tags/multiplexing.md>), [pool](<https://devfeed.tech/tags/pool.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [rds](<https://devfeed.tech/tags/rds.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [transactions](<https://devfeed.tech/tags/transactions.md>)

### AI overview

RDS Proxy multiplexing for PostgreSQL is reduced when sessions are pinned, client identities fragment the pool, or transactions remain open. CloudWatch indicators help distinguish them: elevated session-pinned connections suggest pinning; many backend connections with low borrowing and pinning can indicate fragmentation; sustained borrowing and open transactions point to transactions held too long. Fixes include upgrading the PostgreSQL JDBC driver to 42.7.x or newer, removing application SET statements, setting Spark JDBC writes to isolationLevel=NONE, and using InitQuery for shared session defaults. Standardize username, database, and ApplicationName among clients that should share a pool, while preserving separate users when privilege or audit needs require them. Commit promptly or enable autocommit where explicit transaction control is unnecessary. PostgreSQL targets do not support the proxy's SET pinning filter, and CloudWatch gauges can miss short-lived borrow cycles.

### Source excerpt

RDS Proxy multiplexes many client connections across a small pool of database connections, but connection pinning, pool fragmentation, and uncommitted transactions can silently disable that benefit for PostgreSQL workloads. Part 1 shows how to recognize each condition with Amazon CloudWatch metrics and the fix that restores multiplexing.

## Improve RDS Proxy multiplexing for PostgreSQL, Part 2: Diagnose and monitor

DevFeed: [Improve RDS Proxy multiplexing for PostgreSQL, Part 2: Diagnose and monitor](<https://devfeed.tech/articles/improve-rds-proxy-multiplexing-for-postgresql-part-2-diagnose-and-monitor-133438.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/improve-rds-proxy-multiplexing-for-postgresql-part-2-diagnose-and-monitor/>)

Author: Pavel Rabinovich

Published: 2026-11-13T21:08:04Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon CloudWatch Logs](<https://devfeed.tech/topics/amazon-cloudwatch-logs.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Insight for DBAs](<https://devfeed.tech/topics/insight-for-dbas.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-cloudwatch-logs](<https://devfeed.tech/tags/amazon-cloudwatch-logs.md>), [amazon-emr](<https://devfeed.tech/tags/amazon-emr.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-identity-and-access-management-iam](<https://devfeed.tech/tags/aws-identity-and-access-management-iam.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [diagnose](<https://devfeed.tech/tags/diagnose.md>), [insights](<https://devfeed.tech/tags/insights.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [multiplexing](<https://devfeed.tech/tags/multiplexing.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [rds](<https://devfeed.tech/tags/rds.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [regression](<https://devfeed.tech/tags/regression.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

CloudWatch metrics can show that RDS Proxy multiplexing has degraded, but enhanced proxy logs help explain why and which connections are involved. CloudWatch Logs Insights queries summarize backend connection borrows, releases, and pins, or trace one connection's lifecycle. For user and ApplicationName attribution, the post correlates proxy TCP events with PostgreSQL connection logs using IP:port; this is a best-effort match that depends on a narrow time window and synchronized timestamps. Healthy multiplexing shows many borrows and releases per backend connection, few pins, and substantially fewer backend than client connections. The post recommends alarms for sustained pinning and an elevated backend-to-client connection ratio, with workload-specific baselines and a traffic floor. Enhanced logging produces detailed SQL text, adds log volume, cost, and possible proxy overhead, so restrict log access, use it temporarily, and disable it after diagnosis.

### Source excerpt

Metrics alone can't always pinpoint what is reducing RDS Proxy multiplexing for PostgreSQL. Part 2 shows how to use Amazon CloudWatch Logs Insights with enhanced proxy logs to find the root cause, what healthy multiplexing looks like in metrics and logs, and how to set up CloudWatch alarms that catch regression.

## Boosting Amazon RDS for PostgreSQL with AWS Graviton5: Benchmarks

DevFeed: [Boosting Amazon RDS for PostgreSQL with AWS Graviton5: Benchmarks](<https://devfeed.tech/articles/boosting-amazon-rds-for-postgresql-with-aws-graviton5-benchmarks-131172.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/boosting-amazon-rds-with-aws-graviton5-benchmarks/>)

Author: Angel Duenas

Published: 2026-11-12T23:59:59Z

Content type: comparison

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Graviton](<https://devfeed.tech/topics/graviton.md>), [Benchmark](<https://devfeed.tech/topics/benchmark.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>), [AWS CloudFormation](<https://devfeed.tech/topics/aws-cloudformation.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-block-store-amazon-ebs](<https://devfeed.tech/tags/amazon-elastic-block-store-amazon-ebs.md>), [amazon-elastic-compute-cloud-amazon-ec2](<https://devfeed.tech/tags/amazon-elastic-compute-cloud-amazon-ec2.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [aws-graviton](<https://devfeed.tech/tags/aws-graviton.md>), [aws-secrets-manager](<https://devfeed.tech/tags/aws-secrets-manager.md>), [aws-systems-manager](<https://devfeed.tech/tags/aws-systems-manager.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [graviton5](<https://devfeed.tech/tags/graviton5.md>), [m9g](<https://devfeed.tech/tags/m9g.md>), [performance](<https://devfeed.tech/tags/performance.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [rds](<https://devfeed.tech/tags/rds.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [throughput](<https://devfeed.tech/tags/throughput.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>)

### AI overview

In this Sysbench OLTP read/write benchmark, Graviton5-based M9g delivered the highest throughput among Amazon RDS for PostgreSQL instance generations M6g through M9g, with 55% lower p95 latency than M6g, 92% more queries per dollar than M6g, and 20% more than M8g. Tests used PostgreSQL 17.10, default RDS parameters apart from enforced TLS, io2 storage, a 100-thread workload, and five 30-minute runs per class; reported results are medians. The setup aimed to isolate CPU-generation effects, so gains may differ for workloads with another CPU, memory, and I/O balance. The article says Multi-AZ class changes use automatic failover with minimal downtime, while its tested Single-AZ setup needs a brief reboot, and recommends testing production workloads before upgrading.

### Source excerpt

AWS Graviton5 is now available on Amazon RDS through the new M9g instance family. In this post, we benchmark M9g against the M6g, M7g, and M8g generations for Amazon RDS for PostgreSQL, measuring throughput, latency, and price-performance so you can decide whether an upgrade is worth it.

## Build an Oracle AWR-style report for RDS/Aurora PostgreSQL

DevFeed: [Build an Oracle AWR-style report for RDS/Aurora PostgreSQL](<https://devfeed.tech/articles/build-an-oracle-awr-style-report-for-rds-aurora-postgresql-129581.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/build-an-oracle-awr-style-report-for-rds-aurora-postgresql/>)

Author: Tushar Rajput

Published: 2026-11-11T18:20:16Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [Insight for DBAs](<https://devfeed.tech/topics/insight-for-dbas.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Oracle Database](<https://devfeed.tech/topics/oracle-database.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [based](<https://devfeed.tech/tags/based.md>), [build](<https://devfeed.tech/tags/build.md>), [built-in](<https://devfeed.tech/tags/built-in.md>), [cron](<https://devfeed.tech/tags/cron.md>), [database](<https://devfeed.tech/tags/database.md>), [event](<https://devfeed.tech/tags/event.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [ids](<https://devfeed.tech/tags/ids.md>), [load](<https://devfeed.tech/tags/load.md>), [oracle](<https://devfeed.tech/tags/oracle.md>), [performance](<https://devfeed.tech/tags/performance.md>), [pg-stat-statements](<https://devfeed.tech/tags/pg-stat-statements.md>), [post](<https://devfeed.tech/tags/post.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [rds](<https://devfeed.tech/tags/rds.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [report](<https://devfeed.tech/tags/report.md>), [style](<https://devfeed.tech/tags/style.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The article presents `awr_lite`, a SQL-based AWR-style reporting solution for RDS and Aurora PostgreSQL built from `pg_stat_statements` and `pg_cron`. It stores snapshots every 15 minutes by default, samples active sessions every 10 seconds, and generates reports between snapshot IDs with load, activity, ranked SQL, segment, wait-event, and configuration sections. Installation requires PostgreSQL 14 or later, both extensions, an `rds_superuser` user, parameter changes and a reboot; objects and cron jobs must share the monitored database. Collection runs on the writer, and windows spanning statistics resets have unreliable deltas. Aurora lacks the WAL figures and restricts cron to one database per cluster; other databases need external scheduling. The sampler stores raw query text and client addresses, so the article advises reviewing exposure and report contents before sharing. CloudWatch Database Insights remains useful for continuous one-second graphical wait analysis.

### Source excerpt

PostgreSQL has no built-in Oracle AWR equivalent. This post shows how to build an AWR-style, snapshot-based performance report for Amazon RDS for PostgreSQL and Amazon Aurora PostgreSQL using pg_stat_statements and pg_cron, producing top-SQL, database-activity, wait-event, and load-profile reports between any two snapshot IDs, entirely in SQL.

## ReinDB: read-only performance monitoring for PostgreSQL, first database free

DevFeed: [ReinDB: read-only performance monitoring for PostgreSQL, first database free](<https://devfeed.tech/articles/reindb-read-only-performance-monitoring-for-postgresql-first-database-free-119626.md>)

Original publisher: [Read original article](<https://www.postgresql.org/about/news/reindb-read-only-performance-monitoring-for-postgresql-first-database-free-3432/>)

Published: 2026-11-05T00:00:00Z

Content type: release

Language: en

Sources: [PostgreSQL news](<https://devfeed.tech/sources/postgresql-news.md>)

Topics: [database monitoring](<https://devfeed.tech/topics/database-monitoring.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [sql-server](<https://devfeed.tech/topics/sql-server.md>)

Tags: [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [aws](<https://devfeed.tech/tags/aws.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [database](<https://devfeed.tech/tags/database.md>), [first](<https://devfeed.tech/tags/first.md>), [free](<https://devfeed.tech/tags/free.md>), [google-cloud](<https://devfeed.tech/tags/google-cloud.md>), [linux](<https://devfeed.tech/tags/linux.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [oracle](<https://devfeed.tech/tags/oracle.md>), [performance](<https://devfeed.tech/tags/performance.md>), [performance-monitoring](<https://devfeed.tech/tags/performance-monitoring.md>), [pg-stat-statements](<https://devfeed.tech/tags/pg-stat-statements.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [sql-server](<https://devfeed.tech/tags/sql-server.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

ReinDB monitors PostgreSQL performance by learning each database's and statement's hour-by-hour baseline from pg_stat_statements, then flagging deviations ranked by the extra database time they cost. Flags include supporting evidence such as plan history and a testable fix script with an undo for each step. It requires one read-only login and installs nothing in the database. It can run hosted, onsite on Linux or Windows, or in the customer's AWS or Google Cloud account; MySQL, SQL Server, and Oracle are also supported. The first database is free for one person with no time limit or card requirement.

### Source excerpt

Bandlei has released ReinDB, read-only performance monitoring for PostgreSQL, self-managed or on Amazon RDS and Aurora. ReinDB learns what normal looks like for each database and statement, hour by hour, using pg_stat_statements, and flags what drifts from it, ranked by the extra database time each change costs. Each flag shows the evidence, including plan history, and a fix script your DBA can test, with an undo for each step. ReinDB installs nothing in your database and needs one read-only login. It runs hosted, onsite on Linux or Windows, or in your own AWS or Google Cloud account. MySQL, SQL Server and Oracle are also supported. The first database is free for one person, with no time limit and no card. A free 109-page guide, Rein In Your Database, covers the tuning method behind it. More at reindb.com.

## Implementing PostgreSQL logical replication between Amazon RDS for PostgreSQL instances on separate AWS Outposts

DevFeed: [Implementing PostgreSQL logical replication between Amazon RDS for PostgreSQL instances on separate AWS Outposts](<https://devfeed.tech/articles/implementing-postgresql-logical-replication-between-amazon-rds-for-postgresql-instances-on-separate-aws-outposts-119354.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/implementing-postgresql-logical-replication-between-amazon-rds-for-postgresql-instances-on-separate-aws-outposts/>)

Author: Belma Canik

Published: 2026-11-04T22:02:23Z

Content type: tutorial

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [AWS Outposts](<https://devfeed.tech/topics/aws-outposts.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [all](<https://devfeed.tech/tags/all.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-outposts](<https://devfeed.tech/tags/aws-outposts.md>), [backups](<https://devfeed.tech/tags/backups.md>), [configure](<https://devfeed.tech/tags/configure.md>), [customer](<https://devfeed.tech/tags/customer.md>), [data](<https://devfeed.tech/tags/data.md>), [environment](<https://devfeed.tech/tags/environment.md>), [gateways](<https://devfeed.tech/tags/gateways.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [implementing](<https://devfeed.tech/tags/implementing.md>), [logical](<https://devfeed.tech/tags/logical.md>), [logical-replication](<https://devfeed.tech/tags/logical-replication.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [rds](<https://devfeed.tech/tags/rds.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [replication](<https://devfeed.tech/tags/replication.md>), [separate](<https://devfeed.tech/tags/separate.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

PostgreSQL logical replication between Amazon RDS instances on separate AWS Outposts can keep replication traffic on premises when CoIP addresses route through each rack's Local Gateway and the on-premises network. The setup requires CoIP to be explicitly enabled for each RDS instance, cross-Outpost and same-Outpost hairpin routes, PostgreSQL access on port 5432, and matching table schemas. Enable `rds.logical_replication` on the publisher; grant the replication user `SELECT` on published tables; and include `sslmode=require` in the subscription connection string because RDS PostgreSQL 15+ enforces SSL by default. Monitor replication and synchronization with PostgreSQL's replication status views. The approach provides a manually managed resilience option where regional backups are unacceptable or Multi-AZ prerequisites are unavailable. Multi-AZ offers automatic failover and synchronous replication, but requires Outposts in different Availability Zones and does not support local backups. Local RDS backups require S3 on Outposts capacity and are not supported for Multi-AZ deployments or read replicas.

### Source excerpt

Learn how to configure PostgreSQL logical replication between two Amazon RDS for PostgreSQL instances on separate AWS Outposts racks, keeping all replication traffic and backups within your on-premises environment by using Customer-owned IP addresses and Local Gateways, without any data traversing the AWS Region.

## Zero-Downtime Postgres Migration from RDS to Prisma Postgres

DevFeed: [Zero-Downtime Postgres Migration from RDS to Prisma Postgres](<https://devfeed.tech/articles/zero-downtime-postgres-migration-from-rds-to-prisma-postgres-100727.md>)

Original publisher: [Read original article](<https://www.prisma.io/blog/moving-prismas-control-plane-to-prisma-postgres>)

Author: Kristof Siket; Ankur Datta

Published: 2026-10-26T00:00:00Z

Content type: tutorial

Language: en

Sources: [Prisma](<https://devfeed.tech/sources/prisma-blog.md>)

Topics: [zero downtime deployment](<https://devfeed.tech/topics/zero-downtime-deployment.md>), [Prisma](<https://devfeed.tech/topics/prisma.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [accelerate](<https://devfeed.tech/tags/accelerate.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [logical](<https://devfeed.tech/tags/logical.md>), [logical-replication](<https://devfeed.tech/tags/logical-replication.md>), [migration](<https://devfeed.tech/tags/migration.md>), [open](<https://devfeed.tech/tags/open.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [prisma](<https://devfeed.tech/tags/prisma.md>), [rds](<https://devfeed.tech/tags/rds.md>), [replication](<https://devfeed.tech/tags/replication.md>), [rollback](<https://devfeed.tech/tags/rollback.md>), [tables](<https://devfeed.tech/tags/tables.md>), [using](<https://devfeed.tech/tags/using.md>), [with](<https://devfeed.tech/tags/with.md>), [zero](<https://devfeed.tech/tags/zero.md>)

### AI overview

Prisma moved its 83-table, 74 GB control-plane database from Amazon RDS to Prisma Postgres without pausing writes. Logical replication copied the tables and then streamed row changes; after checking primary keys, schema parity, network access, and per-table row counts, the team switched all six services in one deployment. The last service write reached RDS seven minutes later. A replication slot created just before cutover let RDS follow Prisma Postgres for a week, enabling rollback by changing the connection configuration. The team used `copy_data = false` and Postgres 16's `origin = none` to avoid recopying rows during reverse replication. The process required matching schemas on both databases because logical replication carries row changes, not DDL or sequence values. One migration initially ran only on Prisma Postgres and stopped the reverse stream until the SQL was applied to RDS; no data was lost.

### Source excerpt

How Prisma migrated 83 tables and 74 GB from Amazon RDS to Prisma Postgres with zero downtime using logical replication, and kept a rollback open for a week.

## SafeGrd: PostgreSQL backups that are restored and checked on a schedule

DevFeed: [SafeGrd: PostgreSQL backups that are restored and checked on a schedule](<https://devfeed.tech/articles/safegrd-postgresql-backups-that-are-restored-and-checked-on-a-schedule-100723.md>)

Original publisher: [Read original article](<https://www.postgresql.org/about/news/safegrd-postgresql-backups-that-are-restored-and-checked-on-a-schedule-3414/>)

Published: 2026-10-22T00:00:00Z

Content type: article

Language: en

Sources: [PostgreSQL news](<https://devfeed.tech/sources/postgresql-news.md>)

Topics: [backups](<https://devfeed.tech/topics/backups.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>)

Tags: [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [attestation](<https://devfeed.tech/tags/attestation.md>), [backups](<https://devfeed.tech/tags/backups.md>), [counts](<https://devfeed.tech/tags/counts.md>), [decrypt](<https://devfeed.tech/tags/decrypt.md>), [dump](<https://devfeed.tech/tags/dump.md>), [email](<https://devfeed.tech/tags/email.md>), [encrypted](<https://devfeed.tech/tags/encrypted.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [fire](<https://devfeed.tech/tags/fire.md>), [image](<https://devfeed.tech/tags/image.md>), [lock](<https://devfeed.tech/tags/lock.md>), [managed](<https://devfeed.tech/tags/managed.md>), [memory](<https://devfeed.tech/tags/memory.md>), [neon](<https://devfeed.tech/tags/neon.md>), [null](<https://devfeed.tech/tags/null.md>), [pg-dump](<https://devfeed.tech/tags/pg-dump.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [postgresql-backups](<https://devfeed.tech/tags/postgresql-backups.md>), [schedule](<https://devfeed.tech/tags/schedule.md>)

### AI overview

SafeGrd backs up PostgreSQL 13+ from a nearby host using a read-only database role, encrypts data locally with age, and stores it in an S3 bucket with Object Lock; after the first run, backups upload only changes. Scheduled "Fire Drills" decrypt the newest backup and check it either in memory or in a throwaway PostgreSQL database, including recorded counts, extensions, and optional user SQL checks. Signed, linked records can be verified in a browser. Customers choose customer-managed keys, which only they can decrypt, or SafeGrd-managed keys released to enrolled hosts. The free plan covers one database, with daily hosted backups or hourly backups to a customer bucket and weekly in-memory drills; paid plans start at $15/month and add hourly backups, sandbox drills, and more databases.

### Source excerpt

SafeGrd is a new backup service for PostgreSQL 13 and later that restores every backup on a schedule and checks the row counts. It takes a backup, restores it later into memory or a throwaway database, and counts what came back, so you find out a backup is broken before you need it. Taking the backup The safegrd daemon runs on a host next to your database and connects as a read-only role. On PostgreSQL 14 and later that role only needs pg_read_all_data. On 13 you grant each schema instead. The schema comes from pg_dump and the rows come over binary COPY, in one transaction. After the first run, each backup uploads only what changed. The backup is encrypted with age on your host before it leaves, then written to an S3 bucket with Object Lock on. That can be your own bucket or SafeGrd-hosted storage. The backup data never goes through SafeGrd's servers. You choose how the age key is managed. With a customer-managed key, only you can decrypt these backups. With a SafeGrd-managed key, SafeGrd keeps your key sealed and releases it only to your enrolled hosts, so you can restore even after losing a host. Supabase, Neon and Amazon RDS work from a connection string. Supabase backups are restored on Supabase's own Postgres image, so the extensions in the dump load. Testing the backup We call the restore test a Fire Drill. It takes the newest backup, decrypts it and checks it in one of two ways: In memory. The dump is replayed without a running server, and the table, row and column counts and the extensions are compared with what the backup recorded. In a sandbox. The backup is restored into a throwaway PostgreSQL database and the counts are checked there. You can add your own SQL checks too, for example SELECT count(*) FROM users WHERE email IS NULL has to return 0. Each drill writes a signed, dated record with the counts and the check results. Every record points at the one before it. The attestation verifier checks the whole chain against SafeGrd's published signing key in

## Reducing storage initialization impact in Amazon RDS for PostgreSQL after snapshot restore

DevFeed: [Reducing storage initialization impact in Amazon RDS for PostgreSQL after snapshot restore](<https://devfeed.tech/articles/reducing-storage-initialization-impact-in-amazon-rds-for-postgresql-after-snapshot-restore-87260.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/reducing-storage-initialization-impact-in-amazon-rds-for-postgresql-after-snapshot-restore/>)

Author: Sandeep Modappady

Published: 2026-10-14T15:52:26Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Cloud and systems](<https://devfeed.tech/topics/cloud-and-systems.md>), [lazy loading](<https://devfeed.tech/topics/lazy-loading.md>), [Disaster Recovery](<https://devfeed.tech/topics/disaster-recovery.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-elastic-block-store-amazon-ebs](<https://devfeed.tech/tags/amazon-elastic-block-store-amazon-ebs.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [database-performance](<https://devfeed.tech/tags/database-performance.md>), [disaster-recovery](<https://devfeed.tech/tags/disaster-recovery.md>), [performance](<https://devfeed.tech/tags/performance.md>), [queries](<https://devfeed.tech/tags/queries.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [vacuum](<https://devfeed.tech/tags/vacuum.md>)

### AI overview

After an Amazon RDS for PostgreSQL snapshot restore, lazy loading can make queries slower while EBS blocks are fetched on demand. The article explains using pg_prewarm to hydrate data, why VACUUM ANALYZE provides limited hydration, and how to monitor initialization progress through RDS API fields and the console.

### Source excerpt

When you restore an Amazon RDS for PostgreSQL instance from a snapshot, the Amazon EBS volume hydrates lazily, so early queries can run 10x to 15x slower. This post walks through PostgreSQL-native prewarming techniques (pg_prewarm, VACUUM ANALYZE, and full table scans) and new monitoring fields to restore predictable performance faster after restore.

## AWS Weekly Roundup: Prime Day 2026 by the numbers, Claude Haiku 5.5, Amazon Nova 2.5 Sonic, and more (October 13, 2026)

DevFeed: [AWS Weekly Roundup: Prime Day 2026 by the numbers, Claude Haiku 5.5, Amazon Nova 2.5 Sonic, and more (October 13, 2026)](<https://devfeed.tech/articles/aws-weekly-roundup-prime-day-2026-by-the-numbers-claude-haiku-5-5-amazon-nova-2-5-sonic-and-more-october-13-2026-86343.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/aws/aws-weekly-roundup-prime-day-2026-by-the-numbers-claude-haiku-5-5-amazon-nova-2-5-sonic-and-more-october-13-2026/>)

Author: Daniel Abib

Published: 2026-10-13T15:59:06Z

Content type: news

Language: en

Sources: [AWS News Blog](<https://devfeed.tech/sources/aws-news-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [AWS Network Firewall](<https://devfeed.tech/topics/aws-network-firewall.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Postman Agent Mode](<https://devfeed.tech/topics/postman-agent-mode.md>), [Amazon Cognito](<https://devfeed.tech/topics/amazon-cognito.md>), [Amazon MSK](<https://devfeed.tech/topics/amazon-msk.md>), [Redpanda](<https://devfeed.tech/topics/redpanda-data-streaming.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-mode](<https://devfeed.tech/tags/agent-mode.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-guardduty](<https://devfeed.tech/tags/amazon-guardduty.md>), [amazon-nova](<https://devfeed.tech/tags/amazon-nova.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [amazon-redshift](<https://devfeed.tech/tags/amazon-redshift.md>), [amazon-simple-storage-service-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-s3.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [apache-kafka](<https://devfeed.tech/tags/apache-kafka.md>), [apache-spark](<https://devfeed.tech/tags/apache-spark.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-fault-injection-service-fis](<https://devfeed.tech/tags/aws-fault-injection-service-fis.md>), [aws-glue](<https://devfeed.tech/tags/aws-glue.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [aws-re-invent](<https://devfeed.tech/tags/aws-re-invent.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-haiku-5-5](<https://devfeed.tech/tags/claude-haiku-5-5.md>), [news](<https://devfeed.tech/tags/news.md>), [nova](<https://devfeed.tech/tags/nova.md>), [prime-day](<https://devfeed.tech/tags/prime-day.md>), [strands-agents](<https://devfeed.tech/tags/strands-agents.md>), [week-in-review](<https://devfeed.tech/tags/week-in-review.md>)

### AI overview

This AWS weekly roundup covers Prime Day 2026 infrastructure metrics, including high request volumes across ElastiCache, DynamoDB, Lambda, and EBS, alongside launches and updates involving Claude Haiku 5.5, Nova 2.5 Sonic, GuardDuty, Kafka, and Redshift. It also highlights agent sandboxing and code security tools.

### Source excerpt

Some numbers are hard to picture until you sit with them for a moment. Last week we published the Prime Day 2026 metrics, and the one that stuck with me is 2.3 quadrillion: the daily requests Amazon ElastiCache peaked at during the event. Prime Day ran back in June, so this post always lands as [...]

## Storage layout and best practices for Amazon RDS Custom for SQL Server

DevFeed: [Storage layout and best practices for Amazon RDS Custom for SQL Server](<https://devfeed.tech/articles/storage-layout-and-best-practices-for-amazon-rds-custom-for-sql-server-86352.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/storage-layout-and-best-practices-for-amazon-rds-custom-for-sql-server/>)

Author: Olushola Oladipupo

Published: 2026-10-13T15:26:21Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Cloud and systems](<https://devfeed.tech/topics/cloud-and-systems.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-elastic-block-store-amazon-ebs](<https://devfeed.tech/tags/amazon-elastic-block-store-amazon-ebs.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [amazon-rds-custom](<https://devfeed.tech/tags/amazon-rds-custom.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [backup](<https://devfeed.tech/tags/backup.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [sql-server](<https://devfeed.tech/tags/sql-server.md>)

### AI overview

The article explains how Amazon RDS Custom for SQL Server uses the C:, D:, and W: drives, with W: serving as a raw block replication layer beneath the D: data volume. It provides checks for identifying user attached EBS volumes, warns against modifying managed storage, and outlines safer disk operations and recovery steps.

### Source excerpt

Amazon RDS Custom for SQL Server gives you OS-level access, which also exposes internal storage volumes where the W: drive looks like a raw, uninitialized disk. This post explains the C:, D:, and W: drive architecture, how the drives map to Amazon EBS, and the safe disk operations and verification checks that keep you from accidentally destroying your data.

## Consolidating databases with Postgres logical replication

DevFeed: [Consolidating databases with Postgres logical replication](<https://devfeed.tech/articles/consolidating-databases-with-postgres-logical-replication-65541.md>)

Original publisher: [Read original article](<https://tapoueh.org/blog/2026/10/consolidating-databases-with-postgres-logical-replication/>)

Author: Dimitri Fontaine PostgreSQL Major Contributor; Author

Published: 2026-10-06T11:45:23Z

Content type: article

Language: en

Sources: [Dimitri Fontaine](<https://devfeed.tech/sources/dimitri-fontaine.md>)

Topics: [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [self-hosted databases vs managed services](<https://devfeed.tech/topics/self-hosted-databases-vs-managed-services.md>), [Replication](<https://devfeed.tech/topics/replication.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [databases](<https://devfeed.tech/tags/databases.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [replication](<https://devfeed.tech/tags/replication.md>), [scalability](<https://devfeed.tech/tags/scalability.md>)

### AI overview

The article demonstrates how to consolidate multiple application databases into a PostgreSQL warehouse using logical replication. It covers schema naming, row filters and column lists for limiting replicated data, re-exporting changes as a CDC stream, logical decoding from a standby, and operational gaps such as manual DDL handling and sequence replication. It also explains how behavior varies across PostgreSQL releases and compares core PostgreSQL features with extension-based approaches.

### Source excerpt

This is part 2 of a series about Postgres logical replication use-cases, and about how the feature set has evolved over the past ten years and ten releases, one architecture at a time. Part 1 built a hub-and-workers system for write scalability and has the table of what each release added, which this post assumes. Part 3 covers a zero-downtime major upgrade.

## What is direct I/O, and why does ClickHouse Managed Postgres use it for backups?

DevFeed: [What is direct I/O, and why does ClickHouse Managed Postgres use it for backups?](<https://devfeed.tech/articles/what-is-direct-i-o-and-why-does-clickhouse-managed-postgres-use-it-for-backups-63832.md>)

Original publisher: [Read original article](<https://clickhouse.com/blog/direct-io-managed-postgres-backups>)

Author: Kaushik Iska

Published: 2026-10-02T13:27:05Z

Content type: article

Language: en

Sources: [ClickHouse Blog](<https://devfeed.tech/sources/clickhouse-blog.md>)

Topics: [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>)

Tags: [configuration](<https://devfeed.tech/tags/configuration.md>), [cost](<https://devfeed.tech/tags/cost.md>), [latency](<https://devfeed.tech/tags/latency.md>), [postgres](<https://devfeed.tech/tags/postgres.md>)

### AI overview

ClickHouse Managed Postgres uses Direct I/O to bypass Linux's page cache during backups, preserving warm database pages and reducing query latency and CPU use. Because Direct I/O disables readahead, its configuration sizes reads to the NVMe RAID0 stripe and adjusts parallel readers to the server hardware. In a test on a 48-vCPU server with four NVMe drives and a 467 GB database, stripe-sized Direct I/O backups finished in 71 seconds and avoided evicting a 40 GiB warm table.

### Source excerpt

ClickHouse Managed Postgres uses direct I/O and stripe-sized reads to keep backups fast while protecting the page cache and query latency.

## Babelfish for Aurora PostgreSQL performance tuning

DevFeed: [Babelfish for Aurora PostgreSQL performance tuning](<https://devfeed.tech/articles/babelfish-for-aurora-postgresql-performance-tuning-63563.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/babelfish-for-aurora-postgresql-performance-tuning/>)

Author: Amit Arora

Published: 2026-10-01T16:40:53Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [database-optimization](<https://devfeed.tech/topics/database-optimization.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>)

Tags: [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [babelfish-for-aurora-postgresql](<https://devfeed.tech/tags/babelfish-for-aurora-postgresql.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [optimization](<https://devfeed.tech/tags/optimization.md>), [performance-tuning](<https://devfeed.tech/tags/performance-tuning.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [postgresql-performance](<https://devfeed.tech/tags/postgresql-performance.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The post presents an iterative approach to tuning Babelfish for Aurora PostgreSQL. It covers monitoring bottlenecks, optimizing queries with hints and function volatility settings, tuning database parameters, managing connections, and carrying out maintenance such as VACUUM and ANALYZE.

### Source excerpt

In this post, we show you how to tune Babelfish performance through monitoring, query optimization, parameter tuning, and ongoing maintenance.

## Resolving query plan regressions after a MySQL engine upgrade

DevFeed: [Resolving query plan regressions after a MySQL engine upgrade](<https://devfeed.tech/articles/resolving-query-plan-regressions-after-a-mysql-engine-upgrade-61368.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/resolving-query-plan-regressions-after-a-mysql-engine-upgrade/>)

Author: CHANDANA DA

Published: 2026-09-28T17:22:48Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [MySQL](<https://devfeed.tech/topics/mysql.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [mysql-compatible](<https://devfeed.tech/tags/mysql-compatible.md>), [query](<https://devfeed.tech/tags/query.md>), [rds](<https://devfeed.tech/tags/rds.md>), [rds-for-mysql](<https://devfeed.tech/tags/rds-for-mysql.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

After a major version upgrade on Amazon Aurora MySQL or Amazon RDS for MySQL, query performance can regress as optimizer cost models, defaults, and execution strategies change. The post outlines a diagnostic workflow for identifying which version change affected a query and finding an appropriate fix.

### Source excerpt

After a major or minor version upgrade on Amazon Aurora MySQL or Amazon RDS for MySQL, some queries regress because the optimizer's cost models, defaults, and execution strategies change. This post walks through a diagnostic workflow that traces each regression to the specific version change behind it and applies the right fix.

## Migrate SQL Server multi-result-set procedures to PostgreSQL

DevFeed: [Migrate SQL Server multi-result-set procedures to PostgreSQL](<https://devfeed.tech/articles/migrate-sql-server-multi-result-set-procedures-to-postgresql-57598.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/migrate-sql-server-multi-result-set-procedures-to-postgresql/>)

Author: Ken Zhang

Published: 2026-09-21T16:45:03Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [sql-server](<https://devfeed.tech/topics/sql-server.md>), [Database](<https://devfeed.tech/topics/database.md>), [migration](<https://devfeed.tech/topics/migration.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [.NET](<https://devfeed.tech/topics/net.md>), [JSON](<https://devfeed.tech/topics/json.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [apis](<https://devfeed.tech/tags/apis.md>), [json](<https://devfeed.tech/tags/json.md>), [migrate](<https://devfeed.tech/tags/migrate.md>), [net](<https://devfeed.tech/tags/net.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [postgresql-compatible](<https://devfeed.tech/tags/postgresql-compatible.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [sql-server](<https://devfeed.tech/tags/sql-server.md>), [stored-procedures](<https://devfeed.tech/tags/stored-procedures.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

This tutorial explains how to migrate SQL Server stored procedures that return multiple result sets to PostgreSQL. It compares refcursors with session-scoped temporary tables and JSON aggregation, then covers implementation and validation changes for PostgreSQL and .NET/Npgsql applications.

### Source excerpt

SQL Server stored procedures can return multiple result sets from one call, but PostgreSQL cannot. This post presents two PostgreSQL-native alternatives to refcursors, session-scoped temporary tables and JSON aggregation, compares both against a refcursor baseline, and shows how to implement and validate each in .NET and Npgsql.

## Beyond Self-Managed EC2: NDB on NC2 for RDS Custom for Oracle Databases

DevFeed: [Beyond Self-Managed EC2: NDB on NC2 for RDS Custom for Oracle Databases](<https://devfeed.tech/articles/beyond-self-managed-ec2-ndb-on-nc2-for-rds-custom-for-oracle-databases-79541.md>)

Original publisher: [Read original article](<https://www.nutanix.com/blog/ndb-on-nc2-for-rds-custom-for-oracle-databases>)

Author: Abilash Rengasamy; Daljit Singh

Published: 2026-09-17T10:30:00Z

Content type: article

Language: en

Sources: [Nutanix](<https://devfeed.tech/sources/nutanix.md>)

Topics: [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Oracle Database](<https://devfeed.tech/topics/oracle-database.md>), [amazon](<https://devfeed.tech/topics/amazon.md>)

Tags: [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [brand](<https://devfeed.tech/tags/brand.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [database](<https://devfeed.tech/tags/database.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [failover](<https://devfeed.tech/tags/failover.md>), [high-availability](<https://devfeed.tech/tags/high-availability.md>), [nutanix-cloud-clusters-nc2](<https://devfeed.tech/tags/nutanix-cloud-clusters-nc2.md>), [nutanix-cloud-platform-ncp](<https://devfeed.tech/tags/nutanix-cloud-platform-ncp.md>), [nutanix-database-service-ndb](<https://devfeed.tech/tags/nutanix-database-service-ndb.md>), [oracle-database](<https://devfeed.tech/tags/oracle-database.md>), [rds](<https://devfeed.tech/tags/rds.md>), [support](<https://devfeed.tech/tags/support.md>), [tof-awareness](<https://devfeed.tech/tags/tof-awareness.md>)

### AI overview

AWS plans to end support for RDS Custom for Oracle on March 31, 2027, after which instances, snapshots, and custom engine versions will no longer be accessible. The article presents Nutanix Database Service on Nutanix Cloud Clusters in AWS as an alternative to moving workloads to self-managed EC2, describing its OS-level access and automation for Oracle database operations, including provisioning, high availability, backups, patching, upgrades, and storage scaling.

### Source excerpt

AWS has announced that Amazon RDS Custom for Oracle will reach end of support on March 31, 2027. Customers can continue using the service as-is until then; after that date, RDS Custom for Oracle database instances, snapshots, and custom engine versions will no longer be accessible.

## 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](<https://devfeed.tech/articles/fix-circular-role-dependencies-before-upgrading-amazon-rds-and-amazon-aurora-postgresql-4708.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/resolve-circular-role-dependencies-during-upgrades-of-amazon-rds-for-postgresql-and-amazon-aurora/>)

Author: Ravi Teja Adabala

Published: 2026-08-31T23:42:55Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [Graphs](<https://devfeed.tech/topics/graphs.md>)

Tags: [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [database](<https://devfeed.tech/tags/database.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [sql](<https://devfeed.tech/tags/sql.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### 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.

## Running the Debezium Platform on AWS: PostgreSQL to Amazon Kinesis

DevFeed: [Running the Debezium Platform on AWS: PostgreSQL to Amazon Kinesis](<https://devfeed.tech/articles/running-the-debezium-platform-on-aws-postgresql-to-amazon-kinesis-47520.md>)

Original publisher: [Read original article](<https://debezium.io/blog/2026/07/24/debezium-platform-on-aws-postgres-to-kinesis/>)

Author: Philippe Camus

Published: 2026-07-24T00:00:00Z

Content type: tutorial

Language: en

Sources: [Debezium](<https://devfeed.tech/sources/debezium-io.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [k3s](<https://devfeed.tech/topics/k3s.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Replication](<https://devfeed.tech/topics/replication.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>)

Tags: [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [amazon-web-services](<https://devfeed.tech/tags/amazon-web-services.md>), [aws](<https://devfeed.tech/tags/aws.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [ec2](<https://devfeed.tech/tags/ec2.md>), [iam](<https://devfeed.tech/tags/iam.md>), [k3s](<https://devfeed.tech/tags/k3s.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [replication](<https://devfeed.tech/tags/replication.md>)

### AI overview

A practical guide to running the Debezium Platform on a single-node k3s cluster hosted on Amazon EC2. It configures a change-data-capture pipeline from Amazon RDS for PostgreSQL to Amazon Kinesis, covering AWS IAM, stream naming, logical replication, and deployment automation.

### Source excerpt

In his recent mid-year update, Mario highlighted the incredible work he and his team have done to make the Debezium Platform operational on Kubernetes. So let us take it somewhere concrete: Amazon Web Services. This post stands the Platform up on a single-node k3s cluster on an EC2 instance and builds a real change-data-capture pipeline from Amazon RDS for PostgreSQL to Amazon Kinesis. The deployment itself is done through a couple of simple commands via a companion project that does the heavy lifting, so the focus is the AWS-specific friction that documentation is thin on: IAM for the Kinesis sink, Kinesis stream naming, RDS logical replication, and reading a change event back out of the stream to prove it all works. Read more...

## Best Managed PostgreSQL Hosting in 2026: Compared by Use Case

DevFeed: [Best Managed PostgreSQL Hosting in 2026: Compared by Use Case](<https://devfeed.tech/articles/best-managed-postgresql-hosting-in-2026-compared-by-use-case-82205.md>)

Original publisher: [Read original article](<https://estuary.dev/blog/managed-postgresql-hosting>)

Author: Ruhee Shrestha

Published: 2026-06-18T19:11:39Z

Content type: comparison

Language: en

Sources: [Estuary](<https://devfeed.tech/sources/estuary.md>)

Topics: [self-hosted databases vs managed services](<https://devfeed.tech/topics/self-hosted-databases-vs-managed-services.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Supabase](<https://devfeed.tech/topics/supabase.md>), [cost-optimization](<https://devfeed.tech/topics/cost-optimization.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [best](<https://devfeed.tech/tags/best.md>), [cdc](<https://devfeed.tech/tags/cdc.md>), [compare](<https://devfeed.tech/tags/compare.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [managed](<https://devfeed.tech/tags/managed.md>), [platforms](<https://devfeed.tech/tags/platforms.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [rds](<https://devfeed.tech/tags/rds.md>), [supabase](<https://devfeed.tech/tags/supabase.md>)

### AI overview

This guide compares managed PostgreSQL hosting options by operational use case, including startup needs, cloud ecosystem, change data capture (CDC), time-series workloads, and infrastructure control. It explains how PostgreSQL compatibility, extension support, replication behavior, failover handling, and workload requirements affect provider choice, and discusses when self-hosting may suit teams that need greater control and have the expertise to operate it.

### Source excerpt

Compare the best managed PostgreSQL hosting platforms: RDS, Aurora, Supabase, Neon, AlloyDB, and more. Organized by use case: startups, CDC pipelines, time-series, cloud provider, and control.

## The Best PostgreSQL Hosting for Developers in 2026

DevFeed: [The Best PostgreSQL Hosting for Developers in 2026](<https://devfeed.tech/articles/the-best-postgresql-hosting-for-developers-in-2026-95510.md>)

Original publisher: [Read original article](<https://blog.railway.com/p/best-postgresql-hosting-2026>)

Author: Angelo Saraceno

Published: 2026-05-25T00:00:00Z

Content type: comparison

Language: en

Sources: [Railway](<https://devfeed.tech/sources/railway.md>)

Topics: [hosting](<https://devfeed.tech/topics/hosting.md>), [The Three Main Cloud Service Models](<https://devfeed.tech/topics/the-three-main-cloud-service-models.md>), [Comparing SaaS, PaaS, and IaaS](<https://devfeed.tech/topics/comparing-saas-paas-and-iaas.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Heroku Postgres](<https://devfeed.tech/topics/heroku-postgres.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [best](<https://devfeed.tech/tags/best.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [developers](<https://devfeed.tech/tags/developers.md>), [for-developers](<https://devfeed.tech/tags/for-developers.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [hyperscaler](<https://devfeed.tech/tags/hyperscaler.md>), [net](<https://devfeed.tech/tags/net.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [railway](<https://devfeed.tech/tags/railway.md>), [ranking](<https://devfeed.tech/tags/ranking.md>), [saas](<https://devfeed.tech/tags/saas.md>)

### AI overview

Choose the hosting model before the vendor: integrated PaaS keeps app and database together on one platform and private network; dedicated Postgres SaaS emphasizes database features while you bring compute; hyperscaler services integrate with existing cloud accounts, IAM, and VPCs. The source treats application proximity as a key factor and recommends checking for automatic failover, point-in-time recovery, pooling, extensions, observability, restorable backups, and network adjacency. Neon stands out for copy-on-write branching and scale-to-zero, with cold starts and migration coordination as tradeoffs; Supabase bundles Postgres with auth, storage, and APIs, adding product lock-in. Railway and Render offer app-and-database adjacency, while AWS RDS/Aurora, Google Cloud SQL, and Azure Database for PostgreSQL fit teams already on those clouds. Crunchy Bridge emphasizes Postgres operations; Aiven offers multi-cloud portability at a premium. The rankings reflect the author's perspective, and Railway's entry is by an employee who discloses that affiliation.

### Source excerpt

Postgres hosting fragmented into three shapes in 2026: integrated PaaS, dedicated SaaS, and hyperscaler-native. A ranking that helps you pick the shape before you pick the vendor.

[Next page](<https://devfeed.tech/topics/rds-for-postgresql.md?cursor=WyIyMDI2LTA1LTI1VDAwOjAwOjAwKzAwOjAwIiwgIjZiMGY3Yzk2LTk1YzktNGRiMi05ZjIxLWJlMjMwNzU5ZGFjMCJd>)