Christophe Pettus: Managed Postgres, Examined: Amazon RDS for PostgreSQL
Amazon RDS for PostgreSQL is a managed database service that runs unmodified community PostgreSQL on EC2 instances with EBS storage, offering a straightforward architecture focused on ease of management. It provides automated provisioning, patching, backups, and high availability through AWS's control plane, without forking the PostgreSQL codebase. The service imposes operational constraints such as no shell access, limited superuser privileges, and reliance on AWS-specific mechanisms for replication and failover.
- ▪Amazon RDS for PostgreSQL runs unmodified community PostgreSQL on EC2 instances with EBS storage.
- ▪High availability is achieved through synchronous block-level replication at the EBS layer, not PostgreSQL streaming replication.
- ▪The standby instance in a Multi-AZ deployment is not readable and failover typically takes 60–120 seconds.
- ▪Storage types include gp3, io1, io2, and io2 Block Express, with options for provisioned IOPS and online resizing.
- ▪Users interact with the database via the Postgres wire protocol and AWS APIs, with no direct filesystem or shell access.
Planet PostgreSQL files mainly under programming. We currently carry 28 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Postgr |
| Canonical URL | https://postgr.es/p/9gH |
| Publication time | Tue, 28 Apr 2026 21:00:00 +0000 |
| Retrieval time | 2026-04-28T21:14:39.821Z |
| Last seen | 2026-04-28T21:14:39.821Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | ovO2jFpYPABj |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
2026-04-28 13 min PostgreSQL #RDS Managed Postgres, Examined: Amazon RDS for PostgreSQL First in a series of dispassionate surveys of the major managed-Postgres offerings. This post is about Amazon RDS for PostgreSQL — what AWS calls “traditional RDS,” as distinct from Aurora PostgreSQL, which is a separate product with a separate architecture and will get its own post. Overview Amazon RDS for PostgreSQL is the oldest and most widely deployed managed-Postgres product in the market. The architecture is straightforward: AWS runs community PostgreSQL, unmodified, on an EC2 instance that you don’t have shell access to, backed by EBS storage, with a control plane that handles provisioning, patching, backups, monitoring, and failover.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Postgr.
Discussion
0 commentsMore from Postgr
