# PostgreSQL

PostgreSQL is an open-source object-relational database system.

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

## From instant Aurora PostgreSQL databases to production-ready in your VPC

DevFeed: [From instant Aurora PostgreSQL databases to production-ready in your VPC](<https://devfeed.tech/articles/from-instant-aurora-postgresql-databases-to-production-ready-in-your-vpc-144611.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/from-instant-aurora-postgresql-databases-to-production-ready-in-your-vpc/>)

Author: Saurabh Kothawade

Published: 2026-11-19T22:13:11Z

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>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [ReAct agent Python](<https://devfeed.tech/topics/react-agent-python.md>)

Tags: [access-management](<https://devfeed.tech/tags/access-management.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-vpc](<https://devfeed.tech/tags/amazon-vpc.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [cli](<https://devfeed.tech/tags/cli.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [console](<https://devfeed.tech/tags/console.md>), [data](<https://devfeed.tech/tags/data.md>), [databases](<https://devfeed.tech/tags/databases.md>), [express](<https://devfeed.tech/tags/express.md>), [iam](<https://devfeed.tech/tags/iam.md>), [networking](<https://devfeed.tech/tags/networking.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [production](<https://devfeed.tech/tags/production.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [verify](<https://devfeed.tech/tags/verify.md>), [vpc](<https://devfeed.tech/tags/vpc.md>)

### AI overview

Aurora PostgreSQL clusters created with express configuration can now move into a VPC through one modify operation, keeping their data and endpoint. The move briefly drops existing connections, switches off the internet access gateway, and requires a prepared DB subnet group, security group, private network path for every client, and suitable IAM permissions. Afterward, verify that the cluster is available with VPC networking enabled and the gateway disabled, then confirm clients reconnect; failed moves can return to gateway access and emit an RDS event. The same operation can be run through the console, AWS CLI, or an AI agent. Agent roles can be scoped to approved clusters and explicitly denied permission to move databases back out of a VPC. Creating directly in a VPC is also supported, though it takes longer than the seconds-long default setup. Moving back to gateway access briefly interrupts connections, requires IAM database authentication, and is blocked while VPC-dependent features are active.

### Source excerpt

Amazon Aurora PostgreSQL express configuration now supports VPC networking. You can move an existing cluster into your VPC with a single modify operation, keeping its data and endpoint, from the console, the AWS CLI, or an AI agent. This post shows how to move and verify a cluster, and how to let an agent do it with IAM guardrails.

## Why PostgreSQL 19 shipped late

DevFeed: [Why PostgreSQL 19 shipped late](<https://devfeed.tech/articles/why-postgresql-19-shipped-late-144644.md>)

Original publisher: [Read original article](<https://www.databricks.com/blog/why-postgresql-19-shipped-late>)

Author: Jonathan Katz; Robert Haas

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

Content type: news

Language: en

Sources: [Databricks](<https://devfeed.tech/sources/databricks.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Calculate Pi](<https://devfeed.tech/topics/calculate-pi.md>), [releases](<https://devfeed.tech/topics/releases.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [bug-fixes](<https://devfeed.tech/tags/bug-fixes.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [community](<https://devfeed.tech/tags/community.md>), [contributors](<https://devfeed.tech/tags/contributors.md>), [cves](<https://devfeed.tech/tags/cves.md>), [deferred](<https://devfeed.tech/tags/deferred.md>), [delay](<https://devfeed.tech/tags/delay.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [lakebase](<https://devfeed.tech/tags/lakebase.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [postgresql-19](<https://devfeed.tech/tags/postgresql-19.md>)

### AI overview

PostgreSQL 19 shipped several weeks later than usual because contributors spent time fixing a surge of bugs and security issues in supported branches, leaving less time to review the new release. The authors link the surge to people using newer LLMs to find and report bugs: quarterly updates rose from 1-4 CVEs each through November 2025 to 28 in August 2026, while back-patched commits also increased sharply. The project deferred features that were not ready, and a second release candidate included fixes from the November update. The authors describe the delay as a quality decision and say the community is adapting to AI-assisted bug discovery.

### Source excerpt

PostgreSQL 19 is now generally available, and there are some really cool things in...

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

## PostgreSQL 19 released

DevFeed: [PostgreSQL 19 released](<https://devfeed.tech/articles/postgresql-19-released-144154.md>)

Original publisher: [Read original article](<https://lwn.net/Articles/1108561/>)

Author: jzb

Published: 2026-11-19T16:39:16Z

Content type: release

Language: en

Sources: [LWN.net](<https://devfeed.tech/sources/lwn-net.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>)

Tags: [command](<https://devfeed.tech/tags/command.md>), [concurrently](<https://devfeed.tech/tags/concurrently.md>), [control](<https://devfeed.tech/tags/control.md>), [disruption](<https://devfeed.tech/tags/disruption.md>), [extension](<https://devfeed.tech/tags/extension.md>), [features](<https://devfeed.tech/tags/features.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [introduction](<https://devfeed.tech/tags/introduction.md>), [new-features](<https://devfeed.tech/tags/new-features.md>), [operations](<https://devfeed.tech/tags/operations.md>), [optimize](<https://devfeed.tech/tags/optimize.md>), [performance](<https://devfeed.tech/tags/performance.md>), [pg-plan-advice](<https://devfeed.tech/tags/pg-plan-advice.md>), [plan](<https://devfeed.tech/tags/plan.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [postgresql-19](<https://devfeed.tech/tags/postgresql-19.md>), [query](<https://devfeed.tech/tags/query.md>), [release](<https://devfeed.tech/tags/release.md>), [repack](<https://devfeed.tech/tags/repack.md>), [tables](<https://devfeed.tech/tags/tables.md>)

### AI overview

PostgreSQL 19 introduces `REPACK (CONCURRENTLY)` for optimizing tables without disrupting ongoing operations and the `pg_plan_advice` extension for greater control over plan stability and query performance. The release also includes performance improvements. Several features originally slated for this release were removed; the supplied text does not identify them or detail the full changes, which are covered in the release notes.

### Source excerpt

The PostgreSQL Global Development Group has announced the release of PostgreSQL 19. Notable features in this release include the introduction of the REPACK (CONCURRENTLY) command to optimize tables without disruption to ongoing operations, better control over plan stability and query performance with the new pg_plan_advice extension, and a number of performance improvements. In September, LWN covered the removal of several features initially slated for this release. See the release notes for a full list of new features and changes.

## PostgreSQL 19 Released With More Performance Improvements

DevFeed: [PostgreSQL 19 Released With More Performance Improvements](<https://devfeed.tech/articles/postgresql-19-released-with-more-performance-improvements-143838.md>)

Original publisher: [Read original article](<https://www.phoronix.com/news/PostgreSQL-19-Released>)

Author: Michael Larabel

Published: 2026-11-19T15:57:57Z

Content type: release

Language: en

Sources: [Phoronix](<https://devfeed.tech/sources/phoronix.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>)

Tags: [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [data](<https://devfeed.tech/tags/data.md>), [desktop-linux](<https://devfeed.tech/tags/desktop-linux.md>), [i-o](<https://devfeed.tech/tags/i-o.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [indexes](<https://devfeed.tech/tags/indexes.md>), [insert](<https://devfeed.tech/tags/insert.md>), [jit](<https://devfeed.tech/tags/jit.md>), [linux-benchmarking](<https://devfeed.tech/tags/linux-benchmarking.md>), [linux-hardware-benchmarks](<https://devfeed.tech/tags/linux-hardware-benchmarks.md>), [linux-hardware-reviews](<https://devfeed.tech/tags/linux-hardware-reviews.md>), [linux-how-to](<https://devfeed.tech/tags/linux-how-to.md>), [linux-performance](<https://devfeed.tech/tags/linux-performance.md>), [linux-server-benchmarks](<https://devfeed.tech/tags/linux-server-benchmarks.md>), [logical-replication](<https://devfeed.tech/tags/logical-replication.md>), [open-source-graphics](<https://devfeed.tech/tags/open-source-graphics.md>), [performance](<https://devfeed.tech/tags/performance.md>), [phoronix](<https://devfeed.tech/tags/phoronix.md>), [phoronix-test-suite](<https://devfeed.tech/tags/phoronix-test-suite.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [postgresql-19](<https://devfeed.tech/tags/postgresql-19.md>), [queries](<https://devfeed.tech/tags/queries.md>), [server](<https://devfeed.tech/tags/server.md>), [ubuntu-benchmarks](<https://devfeed.tech/tags/ubuntu-benchmarks.md>), [ubuntu-hardware](<https://devfeed.tech/tags/ubuntu-hardware.md>)

### AI overview

PostgreSQL 19.0 adds workload-management and distributed-data changes, developer features, and performance improvements. The excerpt highlights parallel-worker index vacuuming, faster foreign-key checks, improved queries on foreign tables, logical replication of sequence values, and support for `INSERT ... ON CONFLICT DO SELECT`. It also adds server-side SNI and can adjust I/O worker counts automatically with the default "worker" I/O method. JIT compilation is disabled by default because its cost estimates were considered unreliable; the excerpt says users running many large analytical queries can enable it manually. Benchmark results are not included.

### Source excerpt

After running weeks behind schedule due to PostgreSQL developers being overwhelmed by AI/LLM-led bug reports and security issues, PostgreSQL 19.0 managed to finally ship today...

## PostgreSQL 19 is available on Lakebase

DevFeed: [PostgreSQL 19 is available on Lakebase](<https://devfeed.tech/articles/postgresql-19-is-available-on-lakebase-144643.md>)

Original publisher: [Read original article](<https://www.databricks.com/blog/postgresql-19-available-lakebase>)

Author: Savannah Longoria

Published: 2026-11-19T15:31:46Z

Content type: release

Language: en

Sources: [Databricks](<https://devfeed.tech/sources/databricks.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Insight for DBAs](<https://devfeed.tech/topics/insight-for-dbas.md>), [releases](<https://devfeed.tech/topics/releases.md>)

Tags: [engineering](<https://devfeed.tech/tags/engineering.md>), [lakebase](<https://devfeed.tech/tags/lakebase.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [postgresql-19](<https://devfeed.tech/tags/postgresql-19.md>)

### AI overview

PostgreSQL 19 is available on Lakebase on the day of its general release. The article highlights operational controls: concurrent REPACK can reclaim space and cluster tables while reads and writes continue through most of the job, though it needs extra disk and replication-slot capacity, a suitable replica identity, and a brief final exclusive lock; long transactions can delay that lock, and the described implementation has tuple-change and snapshot-safety limitations. Planner advice can stabilize a diagnosed poor plan, but matching advice does not prove the plan is better. Other changes include parallel index vacuuming and richer diagnostics, logical replication improvements such as sequence synchronization, WAIT FOR LSN for replica read-after-write coordination, and imported remote statistics for postgres_fdw. The article recommends measured adoption, checking required extensions and changed defaults, and notes that PostgreSQL 19.1 is anticipated in February.

### Source excerpt

PostgreSQL 19 reached GA today and it's already available on Lakebase. New major...

## Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oracle

DevFeed: [Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oracle](<https://devfeed.tech/articles/researcher-demonstrates-database-rce-exploits-affecting-postgresql-mysql-and-oracle-142875.md>)

Original publisher: [Read original article](<https://thehackernews.com/2026/11/researcher-demonstrates-database-rce.html>)

Author: The Hacker News

Published: 2026-11-19T08:14:00Z

Content type: news

Language: en

Sources: [Cyber Newsroom](<https://devfeed.tech/sources/cyber-newsroom.md>)

Topics: [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [MySQL](<https://devfeed.tech/topics/mysql.md>), [Oracle Database](<https://devfeed.tech/topics/oracle-database.md>), [Database](<https://devfeed.tech/topics/database.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [application](<https://devfeed.tech/tags/application.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [can](<https://devfeed.tech/tags/can.md>), [code](<https://devfeed.tech/tags/code.md>), [corruption](<https://devfeed.tech/tags/corruption.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-116331](<https://devfeed.tech/tags/cve-2026-116331.md>), [database](<https://devfeed.tech/tags/database.md>), [database-security](<https://devfeed.tech/tags/database-security.md>), [exploits](<https://devfeed.tech/tags/exploits.md>), [memory](<https://devfeed.tech/tags/memory.md>), [memory-corruption](<https://devfeed.tech/tags/memory-corruption.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [oracle](<https://devfeed.tech/tags/oracle.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [rce](<https://devfeed.tech/tags/rce.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [run](<https://devfeed.tech/tags/run.md>), [server](<https://devfeed.tech/tags/server.md>), [software-security](<https://devfeed.tech/tags/software-security.md>), [table](<https://devfeed.tech/tags/table.md>), [this](<https://devfeed.tech/tags/this.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

The researcher's proofs of concept show that limited SQL access can reach memory-unsafe database engine code and lead to server-side code execution, even without access to application tables. PostgreSQL and MySQL attacks use accounts allowed to create temporary objects; the PostgreSQL flaw was fixed, and MySQL's CVE affects Server and Cluster 26.7.0-26.7.1. The Oracle chain is distinct: it combines Oracle Text and Oracle REST Data Services flaws to reach an exposed endpoint without a login; both components have been patched. ClickHouse's reported binary-row-format overflow is triggered by setting `format_binary_max_string_size` to zero; the excerpt gives no CVE or confirmed fix. The researcher reports no known real-world attacks, and the full chains were not independently reproduced. The excerpt recommends installing updates and reviewing temporary-object privileges; that does not address Oracle's no-login path.

### Source excerpt

Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oracle Low-privilege database accounts that cannot read a single application table can still be used to run code on the database server itself, a researcher has shown, by reaching memory-corruption bugs in t ... Read more Published Date: Nov 19, 2026 (2 hours, 45 minutes ago) Vulnerabilities has been mentioned in this article. CVE-2026-114819 CVE-2026-116331 CVE-2026-118383 CVE-2026-91609 CVE-2026-101786

## PostgreSQL 19 Released!

DevFeed: [PostgreSQL 19 Released!](<https://devfeed.tech/articles/postgresql-19-released-144026.md>)

Original publisher: [Read original article](<https://www.postgresql.org/about/news/postgresql-19-released-3449/>)

Author: PostgreSQL Global Development Group

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

Content type: release

Language: en

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

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [rdbms](<https://devfeed.tech/topics/rdbms.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Data Management](<https://devfeed.tech/topics/data-management.md>), [database-scalability](<https://devfeed.tech/topics/database-scalability.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [administration](<https://devfeed.tech/tags/administration.md>), [database](<https://devfeed.tech/tags/database.md>), [developer](<https://devfeed.tech/tags/developer.md>), [development](<https://devfeed.tech/tags/development.md>), [disruption](<https://devfeed.tech/tags/disruption.md>), [extensibility](<https://devfeed.tech/tags/extensibility.md>), [extension](<https://devfeed.tech/tags/extension.md>), [features](<https://devfeed.tech/tags/features.md>), [global](<https://devfeed.tech/tags/global.md>), [global-development](<https://devfeed.tech/tags/global-development.md>), [network](<https://devfeed.tech/tags/network.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [open-source-community](<https://devfeed.tech/tags/open-source-community.md>), [operations](<https://devfeed.tech/tags/operations.md>), [optimize](<https://devfeed.tech/tags/optimize.md>), [organizations](<https://devfeed.tech/tags/organizations.md>), [performance](<https://devfeed.tech/tags/performance.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [postgresql-19](<https://devfeed.tech/tags/postgresql-19.md>)

### AI overview

PostgreSQL 19 adds ways to manage and observe busy workloads with less disruption. `REPACK (CONCURRENTLY)` reclaims table bloat and can reorder data without blocking reads or writes; `pg_plan_advice` stabilizes or experiments with query plans, while `pg_stash_advice` can apply saved advice by query identifier without application changes. Autovacuum gains parallel index vacuuming and table-priority scoring, alongside new monitoring views and I/O reporting. For replication, creating the first logical replication slot automatically raises the effective WAL level to `logical`; `WAIT FOR LSN` lets standby sessions wait for replay before reading recent primary writes. Developer additions include `INSERT ... ON CONFLICT DO SELECT` for get-or-create behavior and JSON output from `COPY`. The release also adds TLS SNI certificate selection, warns after successful MD5 authentication, and removes RADIUS support. JIT is disabled by default because its cost estimates proved unreliable; users running many large analytical queries may choose to enable it.

### Source excerpt

November 19, 2026 - The PostgreSQL Global Development Group today announced the release of PostgreSQL 19, the latest version of the world's most advanced open source database. Mission-critical usage of PostgreSQL continues to rapidly rise, and PostgreSQL 19 responds to this by simplifying both administration and development for these workloads at scale. This release introduces the REPACK (CONCURRENTLY) command so users can optimize tables for their current workload without disruption to ongoing operations. PostgreSQL 19 gives users better control over plan stability and query performance with the new pg_plan_advice extension. Developers will find many delightful features in this release, from support for "read-your-writes" consistency on standbys to "get or create" behavior that saves a network round trip. "For over 30 years, the global open source community has built PostgreSQL into a database that organizations trust with their most critical data," said Jonathan Katz, a member of the PostgreSQL core team. "PostgreSQL 19 continues that commitment to reliability, giving users new ways to manage their workloads without disruption and to build applications that span multiple systems." PostgreSQL, an innovative data management system known for its reliability, robustness, and extensibility, benefits from 30 years of open source development from a global developer community and has become the preferred open source relational database for organizations of all sizes. Simplifying workload management Tables that receive many updates and deletes can build up unused space, known as "bloat," which can also significantly impact query performance. The VACUUM FULL and CLUSTER commands were previously used to handle this, but had tradeoffs, including preventing access to the table until the cleanup finished. PostgreSQL 19 introduces the REPACK command, which reclaims this space and can reorder a table's data to match an index, and with REPACK (CONCURRENTLY), can do so without bloc

## pgjumbo: a new free desktop client for PostgreSQL

DevFeed: [pgjumbo: a new free desktop client for PostgreSQL](<https://devfeed.tech/articles/pgjumbo-a-new-free-desktop-client-for-postgresql-141065.md>)

Original publisher: [Read original article](<https://www.postgresql.org/about/news/pgjumbo-a-new-free-desktop-client-for-postgresql-3444/>)

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

Content type: release

Language: en

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

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [AppImage](<https://devfeed.tech/topics/appimage.md>)

Tags: [administration](<https://devfeed.tech/tags/administration.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [analyze](<https://devfeed.tech/tags/analyze.md>), [apple-silicon](<https://devfeed.tech/tags/apple-silicon.md>), [archive](<https://devfeed.tech/tags/archive.md>), [arm64](<https://devfeed.tech/tags/arm64.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [backup](<https://devfeed.tech/tags/backup.md>), [changes](<https://devfeed.tech/tags/changes.md>), [client](<https://devfeed.tech/tags/client.md>), [completion](<https://devfeed.tech/tags/completion.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [contents](<https://devfeed.tech/tags/contents.md>), [cron](<https://devfeed.tech/tags/cron.md>), [data](<https://devfeed.tech/tags/data.md>), [database](<https://devfeed.tech/tags/database.md>), [deb](<https://devfeed.tech/tags/deb.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [free](<https://devfeed.tech/tags/free.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>)

### AI overview

pgjumbo is a free desktop client for PostgreSQL 12+ on Windows, macOS, and Linux, including Amazon Aurora and RDS with IAM authentication. It can connect directly, over SSL, or through an SSH tunnel. Version 1.0.2 combines schema inspection, a query tool with completion and EXPLAIN views, and a data editor that previews statements before saving. Backup and restore use PostgreSQL's pg_dump tools and support selecting objects or rows, inspecting archive contents, and restoring to a new database. Maintenance tools cover VACUUM, ANALYZE, REINDEX, and per-table autovacuum settings. Object changes are shown as SQL for review; destructive statements on servers marked Production require confirmation.

### Source excerpt

pgjumbo is a new desktop client for PostgreSQL 12+, free to use, for Windows, macOS and Linux, with query, data and administration tools. pgjumbo connects to PostgreSQL 12+, including Amazon Aurora and RDS with IAM authentication, directly, over SSL or through an SSH tunnel. Installers are available for Windows (x64 and ARM64), macOS (Apple silicon and Intel) and Linux (AppImage, .deb and .rpm). Version 1.0.2 includes: An object explorer and inspector with each object's CREATE script, statistics and dependencies. A Query Tool with completion, syntax errors from PostgreSQL's own parser as you type, parameters, EXPLAIN as a table or a diagram, and results that can be sorted, filtered, compared and exported. A data editor that shows the statements before it saves them. Backup and restore built on pg_dump, pg_dumpall and pg_restore: choosing objects and rows, server backups as a folder of archives, reading an archive's contents before restoring, and restoring into a new database. Maintenance: what each table needs and what holds VACUUM back, VACUUM, ANALYZE and REINDEX as reviewed steps with progress, and autovacuum settings per table. Server activity, configuration, roles and privileges, logs, replication, pg_cron jobs and LISTEN/NOTIFY. Changes to objects are shown as SQL and reviewed before they run, and on servers marked Production, destructive statements ask for confirmation first. Download pgjumbo - Release notes for 1.0.2

## pg\_fastload 1.0.0 released: parallel bulk loading for PostgreSQL

DevFeed: [pg\_fastload 1.0.0 released: parallel bulk loading for PostgreSQL](<https://devfeed.tech/articles/pg-fastload-1-0-0-released-parallel-bulk-loading-for-postgresql-137837.md>)

Original publisher: [Read original article](<https://www.postgresql.org/about/news/pg_fastload-100-released-parallel-bulk-loading-for-postgresql-3445/>)

Author: Pg Fastload

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

Content type: release

Language: en

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

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [CSV](<https://devfeed.tech/topics/csv.md>), [IO](<https://devfeed.tech/topics/io.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [background](<https://devfeed.tech/tags/background.md>), [cache](<https://devfeed.tech/tags/cache.md>), [column](<https://devfeed.tech/tags/column.md>), [copy](<https://devfeed.tech/tags/copy.md>), [core](<https://devfeed.tech/tags/core.md>), [csv](<https://devfeed.tech/tags/csv.md>), [data](<https://devfeed.tech/tags/data.md>), [encoding](<https://devfeed.tech/tags/encoding.md>), [export](<https://devfeed.tech/tags/export.md>), [faster](<https://devfeed.tech/tags/faster.md>), [fields](<https://devfeed.tech/tags/fields.md>), [file](<https://devfeed.tech/tags/file.md>), [filter](<https://devfeed.tech/tags/filter.md>), [fork](<https://devfeed.tech/tags/fork.md>), [format](<https://devfeed.tech/tags/format.md>), [function](<https://devfeed.tech/tags/function.md>), [loading](<https://devfeed.tech/tags/loading.md>), [parallel](<https://devfeed.tech/tags/parallel.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>)

### AI overview

pg_fastload 1.0.0 parallelizes reading, parsing, and tuple formation across background workers while the issuing backend serially inserts rows, keeping the load in one transaction. A single reader scans the file once and sends chunks to parser workers, so total input read remains one file size. It is a source-level fork of pg_bulkload 3.1.23 and preserves its control-file syntax, TYPE values, log format, and WRITER modes. The parallel path falls back automatically, with an INFO message, for unsupported conditions including FILTER, explicit ENCODING, constraints, PARSE_ERRORS tolerance, STDIN, and TUPLE or FUNCTION input. In the cited 1 GiB CSV test, default 15-worker pg_fastload took 1.37 seconds versus 5.81 seconds serial pg_fastload, 6.98 seconds for upstream pg_bulkload's fastest mode, and 8.32 seconds for COPY FROM. Results depend on the reported workload and hardware; the excerpt also describes progress reporting, snapshot-auditable exports, and optional index dropping during loads.

### Source excerpt

pg_fastload 1.0.0 is a parallel bulk loader for PostgreSQL, 1.58x faster than the best pg_bulkload mode and 6.07x faster than COPY. It parallelises the loading pipeline across background workers while keeping the load inside a single transaction. It is a source-level fork of pg_bulkload 3.1.23, so control-file syntax, TYPE values, log format and WRITER modes are unchanged. Repository: github.com/yuansong/pg_fastload Release: pg_fastload v1.0.0 License: BSD 3-Clause, with the upstream pg_bulkload copyright notices retained The problem pg_bulkload and COPY both run the whole load in one backend: read, parse, form the tuple, write. On a 16-core machine that leaves 15 cores idle, and the parse step is usually the expensive one. For CSV it is a byte-at-a-time state machine followed by a type input function per column. How it works The load has four stages: read input, parse record and split fields, form the tuple, and insert. Stages 1-3 move to background workers; stage 4 stays serial in the backend that issued the load: one reader worker -> N parser workers -> leader writes Design points that matter in practice: The input file is read exactly once. A single reader scans sequentially and hands chunks to the workers over shm_mq; the workers never open the file. Total read volume stays at 1x the file size, so the speedup does not invert once the data is larger than the page cache. It is still one transaction. No second connection, no early visibility of uncommitted rows, and a bad row aborts the whole load rather than leaving a worker-timing-dependent subset behind. 13 conditions the parallel path cannot honour fall back automatically, with one INFO line saying why: FILTER and FORCE_NOT_NULL, explicit ENCODING, NOT NULL or CHECK constraints, PARSE_ERRORS tolerance, STDIN input, TUPLE and FUNCTION input, and others. The serial path itself was optimised. Records without quotes or CRs take a memchr bulk split instead of the byte-at-a-time loop. Progress reporting and export E

## Open Source DocumentDB 1.0 Reaches General Availability

DevFeed: [Open Source DocumentDB 1.0 Reaches General Availability](<https://devfeed.tech/articles/open-source-documentdb-1-0-reaches-general-availability-133652.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/mongodb-compatible-documentdb/>)

Author: Renato Losio

Published: 2026-11-14T06:37:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [17](<https://devfeed.tech/tags/17.md>), [2025](<https://devfeed.tech/tags/2025.md>), [aggregation](<https://devfeed.tech/tags/aggregation.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-ml-data-engineering](<https://devfeed.tech/tags/ai-ml-data-engineering.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-documentdb](<https://devfeed.tech/tags/amazon-documentdb.md>), [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [aws](<https://devfeed.tech/tags/aws.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [cosmos](<https://devfeed.tech/tags/cosmos.md>), [database](<https://devfeed.tech/tags/database.md>), [drivers](<https://devfeed.tech/tags/drivers.md>), [general-availability](<https://devfeed.tech/tags/general-availability.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [mit](<https://devfeed.tech/tags/mit.md>), [ml-data-engineering](<https://devfeed.tech/tags/ml-data-engineering.md>), [mongodb](<https://devfeed.tech/tags/mongodb.md>), [mongodb-compatible-documentdb](<https://devfeed.tech/tags/mongodb-compatible-documentdb.md>), [news](<https://devfeed.tech/tags/news.md>), [nosql](<https://devfeed.tech/tags/nosql.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [queries](<https://devfeed.tech/tags/queries.md>), [release](<https://devfeed.tech/tags/release.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

DocumentDB 1.0 is the first generally available release of an MIT-licensed, PostgreSQL-based document database with MongoDB wire protocol compatibility. It combines a PostgreSQL extension providing MongoDB API-compatible functionality with a gateway that translates MongoDB protocol requests into PostgreSQL calls; most MongoDB drivers, tools, and queries work without changes. It supports PostgreSQL 15-18 via container images, with Linux packages for versions 17 and 18, and includes a Kubernetes operator. The GA emphasizes security, stability, and fixes for indexing, aggregation, and geospatial queries. DocumentDB supplies its own gateway; FerretDB is a separate project that uses the extensions as its backend and provides a separate compatible interface. An initial YCSB comparison reported 20-33% higher read throughput for DocumentDB and lower update tail latency for FerretDB in mixed workloads, but was not conclusive. An unverified GitHub issue reports higher query latency for DocumentDB 1.0 than MongoDB 9.0.4.

### Source excerpt

DocumentDB 1.0 is the first generally available release of the open source, MIT-licensed document database built on PostgreSQL, with compatibility for the MongoDB wire protocol. Most MongoDB drivers, tools, and queries work without changes. By Renato Losio

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

## PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE

DevFeed: [PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE](<https://devfeed.tech/articles/postgresql-patches-52-flaws-including-22-year-old-bug-enabling-authenticated-rce-133216.md>)

Original publisher: [Read original article](<https://thehackernews.com/2026/11/postgresql-patches-52-flaws-including.html>)

Author: The Hacker News

Published: 2026-11-13T16:53:08Z

Content type: news

Language: en

Sources: [Cyber Newsroom](<https://devfeed.tech/sources/cyber-newsroom.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [patches](<https://devfeed.tech/topics/patches.md>), [Security research](<https://devfeed.tech/topics/security-research.md>)

Tags: [alloydb](<https://devfeed.tech/tags/alloydb.md>), [archive](<https://devfeed.tech/tags/archive.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-aurora](<https://devfeed.tech/tags/aws-aurora.md>), [azure](<https://devfeed.tech/tags/azure.md>), [c-language](<https://devfeed.tech/tags/c-language.md>), [client](<https://devfeed.tech/tags/client.md>), [cloud-security](<https://devfeed.tech/tags/cloud-security.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-6460](<https://devfeed.tech/tags/cve-2026-6460.md>), [database](<https://devfeed.tech/tags/database.md>), [database-security](<https://devfeed.tech/tags/database-security.md>), [patches](<https://devfeed.tech/tags/patches.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [rce](<https://devfeed.tech/tags/rce.md>), [run](<https://devfeed.tech/tags/run.md>), [security](<https://devfeed.tech/tags/security.md>), [security-updates](<https://devfeed.tech/tags/security-updates.md>), [server](<https://devfeed.tech/tags/server.md>), [type](<https://devfeed.tech/tags/type.md>), [updates](<https://devfeed.tech/tags/updates.md>), [user](<https://devfeed.tech/tags/user.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

PostgreSQL's CVE-2026-6460 is a type confusion flaw that can let a database user able to create or modify objects execute code with the operating-system account's privileges. It affects versions before 18.7, 17.12, 16.16, 15.20, and 14.25. The fix adds checks for values whose composite field types have changed; full protection also requires rebuilding C-language extensions. An exploit writeup demonstrates a crash and memory-address leak, but omits the final command-execution step. The sources do not establish whether default-privilege accounts can reach code execution, and the project reports no known exploitation. Administrators should update the matching server and client tools, rebuild extensions, and follow the release's reindexing and backup guidance. The release also fixes 51 other flaws, including an unauthenticated restart issue affecting PostgreSQL 18 and code-execution risks in pg_restore and psql.

### Source excerpt

PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE A type confusion flaw in PostgreSQL lets a database user who can create objects run code on the server. Updates released yesterday fix it, along with 51 other security flaws. Full protection from this ... Read more Published Date: Nov 13, 2026 (3 hours, 32 minutes ago) Vulnerabilities has been mentioned in this article. CVE-2026-6460 CVE-2026-116322

## CVE-2026-95613 - Zenitel Connect pREST API adopts arbitrary PostgreSQL role from unvalidated JWT sub claim

DevFeed: [CVE-2026-95613 - Zenitel Connect pREST API adopts arbitrary PostgreSQL role from unvalidated JWT sub claim](<https://devfeed.tech/articles/cve-2026-95613-zenitel-connect-prest-api-adopts-arbitrary-postgresql-role-from-unvalidated-jwt-sub-claim-132487.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-95613>)

Author: CVEFEED.io

Published: 2026-11-13T16:19:38Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [REST API](<https://devfeed.tech/topics/rest-api.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [api](<https://devfeed.tech/tags/api.md>), [ca](<https://devfeed.tech/tags/ca.md>), [connect](<https://devfeed.tech/tags/connect.md>), [container](<https://devfeed.tech/tags/container.md>), [containers](<https://devfeed.tech/tags/containers.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-95613](<https://devfeed.tech/tags/cve-2026-95613.md>), [data-volume](<https://devfeed.tech/tags/data-volume.md>), [database](<https://devfeed.tech/tags/database.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [filesystem](<https://devfeed.tech/tags/filesystem.md>), [firmware](<https://devfeed.tech/tags/firmware.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [password](<https://devfeed.tech/tags/password.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [private-key](<https://devfeed.tech/tags/private-key.md>), [rest](<https://devfeed.tech/tags/rest.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>)

### AI overview

In Zenitel Connect firmware before 1.11.0, the pREST API sets the PostgreSQL session role from an unvalidated JWT `sub` claim while connected as the `postgres` superuser. The API signs and verifies tokens using a platform CA private key stored on a data volume shared between containers. A local attacker who can read that key can forge a JWT with `sub=postgres` and use the API to perform database operations as the superuser, including reading the master encryption key and password hashes. The excerpt reports no affected products in its product table, so it does not identify specific product versions beyond the firmware range in the description.

### Source excerpt

CVE ID :CVE-2026-95613 Published : Nov. 13, 2026, 4:19 p.m. | 1 hour ago Description :The pREST database REST API in Zenitel Connect firmware before 1.11.0 signs and verifies JWTs with the platform CA private key, which is stored on a data volume shared between containers, and sets the PostgreSQL session role from the unvalidated sub claim of each request while connected to the database as the "postgres" superuser, which allows local attackers who can read the platform CA private key from the container filesystem to execute database operations as the PostgreSQL superuser, including reading the master encryption key and password hashes, via a forged JWT with sub=postgres sent to the pREST API. Severity: 8.6 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## PostgreSQL extensions: why the FUD is wrong

DevFeed: [PostgreSQL extensions: why the FUD is wrong](<https://devfeed.tech/articles/postgresql-extensions-why-the-fud-is-wrong-132624.md>)

Original publisher: [Read original article](<https://www.red-gate.com/simple-talk/databases/postgresql/postgresql-extensions-why-the-fud-is-wrong/>)

Author: Grant Fritchey

Published: 2026-11-13T12:00:00Z

Content type: opinion

Language: en

Sources: [Simple Talk](<https://devfeed.tech/sources/simple-talk.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [The Three Main Cloud Service Models](<https://devfeed.tech/topics/the-three-main-cloud-service-models.md>)

Tags: [cloud](<https://devfeed.tech/tags/cloud.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [database](<https://devfeed.tech/tags/database.md>), [database-administration](<https://devfeed.tech/tags/database-administration.md>), [databases](<https://devfeed.tech/tags/databases.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [featured](<https://devfeed.tech/tags/featured.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [risk](<https://devfeed.tech/tags/risk.md>), [sql](<https://devfeed.tech/tags/sql.md>), [support](<https://devfeed.tech/tags/support.md>)

### AI overview

PostgreSQL extensions add real upkeep and compatibility work, but the article argues those tradeoffs are manageable and often overstated. Extensions are installed per database and upgraded separately from PostgreSQL core; there is no built-in mechanism to find or install their updates, so teams must track versions across databases and clusters. Abandonment is possible, though the article cites pgBackRest's rapid recovery of corporate support and open source's ability to be forked. Cloud availability depends on the service model and architecture: VMs can run extensions unavailable on some PaaS or DBaaS platforms. The article estimates that about 15% of roughly 575 cataloged extensions have cloud support, including widely used options such as PostGIS, pgvector, pg_stat_statements, pgcrypto, and pg_trgm. It concludes that these risks resemble other software maintenance responsibilities and do not, by themselves, negate extensions' value.

### Source excerpt

PostgreSQL extensions get blamed for maintenance risk, abandonment, and poor cloud support. Here's why that reputation is mostly FUD - not fact.... The post PostgreSQL extensions: why the FUD is wrong appeared first on Simple Talk.

## ZDI-26-974: PostgreSQL pg\_stat\_statements Extension Heap-based Buffer Overflow Remote Code Execution Vulnerability

DevFeed: [ZDI-26-974: PostgreSQL pg\_stat\_statements Extension Heap-based Buffer Overflow Remote Code Execution Vulnerability](<https://devfeed.tech/articles/zdi-26-974-postgresql-pg-stat-statements-extension-heap-based-buffer-overflow-remote-code-execution-vulnerability-133799.md>)

Original publisher: [Read original article](<http://www.zerodayinitiative.com/advisories/ZDI-26-974/>)

Published: 2026-11-13T06:00:00Z

Content type: news

Language: en

Sources: [Zero Day Initiative](<https://devfeed.tech/sources/zero-day-initiative.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [heap overflow](<https://devfeed.tech/topics/heap-overflow.md>), [Exploit](<https://devfeed.tech/topics/exploit.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [allows](<https://devfeed.tech/tags/allows.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [based](<https://devfeed.tech/tags/based.md>), [buffer](<https://devfeed.tech/tags/buffer.md>), [buffer-overflow](<https://devfeed.tech/tags/buffer-overflow.md>), [code](<https://devfeed.tech/tags/code.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [execution](<https://devfeed.tech/tags/execution.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [extension](<https://devfeed.tech/tags/extension.md>), [heap](<https://devfeed.tech/tags/heap.md>), [installations](<https://devfeed.tech/tags/installations.md>), [pg-stat-statements](<https://devfeed.tech/tags/pg-stat-statements.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [remote](<https://devfeed.tech/tags/remote.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [remote-code-execution-vulnerability](<https://devfeed.tech/tags/remote-code-execution-vulnerability.md>), [required](<https://devfeed.tech/tags/required.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

A heap-based buffer overflow in PostgreSQL's pg_stat_statements query-normalization processing can let an authenticated remote attacker execute code as the service account. The flaw occurs when user-supplied data is copied into a heap buffer without validating its length. PostgreSQL has issued an update to correct it; the excerpt links to the relevant commit. The advisory assigns CVE-2026-14676 and CVSS 8.8.

### Source excerpt

This vulnerability allows remote attackers to execute arbitrary code on affected installations of PostgreSQL. Authentication is required to exploit this vulnerability. The ZDI has assigned a CVSS rating of 8.8. The following CVEs are assigned: CVE-2026-14676.

## Why So Many AI Prototypes Never Make It Past the Database

DevFeed: [Why So Many AI Prototypes Never Make It Past the Database](<https://devfeed.tech/articles/why-so-many-ai-prototypes-never-make-it-past-the-database-130616.md>)

Original publisher: [Read original article](<https://sdtimes.com/database/why-so-many-ai-prototypes-never-make-it-past-the-database/>)

Author: Dave Page

Published: 2026-11-12T16:33:09Z

Content type: opinion

Language: en

Sources: [SD Times](<https://devfeed.tech/sources/sd-times.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Database](<https://devfeed.tech/topics/database.md>), [database-scalability](<https://devfeed.tech/topics/database-scalability.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [implementation](<https://devfeed.tech/topics/implementation.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [backups](<https://devfeed.tech/tags/backups.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [database](<https://devfeed.tech/tags/database.md>), [dba](<https://devfeed.tech/tags/dba.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [design](<https://devfeed.tech/tags/design.md>), [guest-view](<https://devfeed.tech/tags/guest-view.md>), [pgedge](<https://devfeed.tech/tags/pgedge.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [prototypes](<https://devfeed.tech/tags/prototypes.md>)

### AI overview

AI coding agents can provision databases quickly with default settings, which can help prototypes but may leave production needs unaddressed. The excerpt highlights reliability under real traffic, deployment flexibility, backups and failover, and data location as issues that need deliberate review. A selected region may cover the primary database and backups while overlooking logs: PostgreSQL error logs can include duplicate values from unique constraint violations, and logs may be sent to a model hosted outside the intended region. Queries that work on hundreds of rows may also become slow at millions. The author recommends defining production requirements during design, including data-region boundaries and acceptable write-loss limits, then testing and auditing them before launch. A database-experienced reviewer should assess production-bound systems; demos with test data may not need the same review, but sensitive data should not be loaded before preparation.

### Source excerpt

Originally, I began using PostgreSQL around 1997 at a UK social housing provider where I was head of IT. We chose Postgres (which at the time was version 6.3.2) so that tenants could see their rent accounts online without per-user licensing costs for the internal system. While a great deal has changed since then, the... ... continue reading The post Why So Many AI Prototypes Never Make It Past the Database appeared first on SD Times.

## PostgreSQL Sees New Releases For 52 Security Vulnerabilities, 140+ Bug Fixes

DevFeed: [PostgreSQL Sees New Releases For 52 Security Vulnerabilities, 140+ Bug Fixes](<https://devfeed.tech/articles/postgresql-sees-new-releases-for-52-security-vulnerabilities-140-bug-fixes-130578.md>)

Original publisher: [Read original article](<https://www.phoronix.com/news/PostgreSQL-52-CVEs>)

Author: Michael Larabel

Published: 2026-11-12T15:56:44Z

Content type: news

Language: en

Sources: [Phoronix](<https://devfeed.tech/sources/phoronix.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [releases](<https://devfeed.tech/topics/releases.md>), [bugfixes](<https://devfeed.tech/topics/bugfixes.md>)

Tags: [aggregate](<https://devfeed.tech/tags/aggregate.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-llms](<https://devfeed.tech/tags/ai-llms.md>), [alter](<https://devfeed.tech/tags/alter.md>), [archive](<https://devfeed.tech/tags/archive.md>), [array](<https://devfeed.tech/tags/array.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [b-tree](<https://devfeed.tech/tags/b-tree.md>), [backup](<https://devfeed.tech/tags/backup.md>), [batch](<https://devfeed.tech/tags/batch.md>), [batch-insert](<https://devfeed.tech/tags/batch-insert.md>), [buffer](<https://devfeed.tech/tags/buffer.md>), [bug](<https://devfeed.tech/tags/bug.md>), [bug-fixes](<https://devfeed.tech/tags/bug-fixes.md>), [desktop-linux](<https://devfeed.tech/tags/desktop-linux.md>), [linux-benchmarking](<https://devfeed.tech/tags/linux-benchmarking.md>), [linux-hardware-benchmarks](<https://devfeed.tech/tags/linux-hardware-benchmarks.md>), [linux-hardware-reviews](<https://devfeed.tech/tags/linux-hardware-reviews.md>), [linux-how-to](<https://devfeed.tech/tags/linux-how-to.md>), [linux-performance](<https://devfeed.tech/tags/linux-performance.md>), [linux-server-benchmarks](<https://devfeed.tech/tags/linux-server-benchmarks.md>), [new-releases](<https://devfeed.tech/tags/new-releases.md>), [open-source-graphics](<https://devfeed.tech/tags/open-source-graphics.md>), [phoronix](<https://devfeed.tech/tags/phoronix.md>), [phoronix-test-suite](<https://devfeed.tech/tags/phoronix-test-suite.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [releases](<https://devfeed.tech/tags/releases.md>), [security](<https://devfeed.tech/tags/security.md>), [security-vulnerabilities](<https://devfeed.tech/tags/security-vulnerabilities.md>), [ubuntu-benchmarks](<https://devfeed.tech/tags/ubuntu-benchmarks.md>), [ubuntu-hardware](<https://devfeed.tech/tags/ubuntu-hardware.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

PostgreSQL released updates for versions 18, 17, 16, 15 and 14, alongside PostgreSQL 19 RC2, to address 52 disclosed security vulnerabilities and more than 140 known bugs. The listed issues include multiple arbitrary-code-execution flaws, as well as SQL injection, memory disclosure, privilege and row-security bypasses, and buffer errors; several carry CVSS v3.1 scores of 8.8. The text identifies this as the final PostgreSQL 15 release, marking that version's end of life, and says PostgreSQL 19 stable is nearing release. It does not provide upgrade instructions or map individual vulnerabilities to affected versions.

### Source excerpt

PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25, and 19 RC2 all released today due to 52 new security issues being disclosed...

## CVE-2026-120148 - PostgreSQL extended-statistics pseudo-type confusion executes arbitrary code

DevFeed: [CVE-2026-120148 - PostgreSQL extended-statistics pseudo-type confusion executes arbitrary code](<https://devfeed.tech/articles/cve-2026-120148-postgresql-extended-statistics-pseudo-type-confusion-executes-arbitrary-code-130520.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-120148>)

Author: CVEFEED.io

Published: 2026-11-12T15:17:43Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [cve-2026-120148](<https://devfeed.tech/tags/cve-2026-120148.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>)

### AI overview

PostgreSQL extended-statistics type confusion can let an object creator execute arbitrary code with the operating-system privileges of the database process. The described mechanism is an extended-statistics expression using an anonymous RECORD type whose backend-local type identifier can refer to a different row type in another session. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. The excerpt lists severity 8.1 (High) and says remote exploitation is not indicated.

### Source excerpt

CVE ID :CVE-2026-120148 Published : Nov. 12, 2026, 3:17 p.m. | 2 hours, 6 minutes ago Description :Type confusion in PostgreSQL extended statistics allows an object creator to execute arbitrary code as the operating system user running the database, via a statistics expression of an anonymous RECORD type whose backend-local type identifier denotes a different row type in another session. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. Severity: 8.1 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Ten ways a glibc change can break your PostgreSQL cluster

DevFeed: [Ten ways a glibc change can break your PostgreSQL cluster](<https://devfeed.tech/articles/ten-ways-a-glibc-change-can-break-your-postgresql-cluster-129676.md>)

Original publisher: [Read original article](<https://www.percona.com/blog/ten-ways-a-glibc-change-can-break-your-postgresql-cluster/>)

Author: Pablo Svampa

Published: 2026-11-11T20:46:25Z

Content type: article

Language: en

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

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [comparison](<https://devfeed.tech/tags/comparison.md>), [corruption](<https://devfeed.tech/tags/corruption.md>), [database](<https://devfeed.tech/tags/database.md>), [glibc](<https://devfeed.tech/tags/glibc.md>), [insight-for-dbas](<https://devfeed.tech/tags/insight-for-dbas.md>), [insight-for-developers](<https://devfeed.tech/tags/insight-for-developers.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [text](<https://devfeed.tech/tags/text.md>)

### AI overview

glibc locale changes can leave PostgreSQL data and behavior inconsistent after an upgrade; rebuilding indexes alone may not repair the damage. The article demonstrates effects including missed index lookups, accepted duplicates, broken foreign-key enforcement, misplaced partition rows, stale CHECK constraints and generated values, and changed text-range results. It recommends diagnosing indexes with amcheck, auditing stored rows and constraints, removing duplicates where needed, moving mispartitioned rows, recomputing generated values and materialized views, then refreshing collation versions and running ANALYZE. Order matters: refresh materialized views only after rebuilding their source indexes, and refresh the collation version last. Some range-query changes are valid under the new locale rules and have no repair; review affected queries. The described audit queries cover columns but not expressions, and the author notes they may still be incomplete.

### Source excerpt

Between any two glibc versions, locales can change, and those changes alter the order of character string comparison (text/varchar/char/citext). It may also happen that locales are removed, such as en_US@ampm, present in RHEL8 and removed in RHEL9, and aa_ER@saaho, present in RHEL9 and then renamed to ssy_ER in RHEL10. Since PostgreSQL relies on locales to ... Continued The post Ten ways a glibc change can break your PostgreSQL cluster appeared first on Percona.

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

## CoreWeave Database Is Here: Managed PostgreSQL Where Your AI Runs

DevFeed: [CoreWeave Database Is Here: Managed PostgreSQL Where Your AI Runs](<https://devfeed.tech/articles/coreweave-database-is-here-managed-postgresql-where-your-ai-runs-129191.md>)

Original publisher: [Read original article](<https://wf.coreweave.com/blog/coreweave-database-is-here-managed-postgresql-where-your-ai-runs>)

Author: CoreWeave

Published: 2026-11-11T16:05:56Z

Content type: release

Language: en

Sources: [Coreweave Blog Posts](<https://devfeed.tech/sources/coreweave-blog-posts.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [CloudNativePG](<https://devfeed.tech/topics/cloudnativepg.md>), [Managed Services](<https://devfeed.tech/topics/managed-services.md>), [Database](<https://devfeed.tech/topics/database.md>), [read-replica](<https://devfeed.tech/topics/read-replica.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [blog](<https://devfeed.tech/tags/blog.md>), [cks](<https://devfeed.tech/tags/cks.md>), [cloudnativepg](<https://devfeed.tech/tags/cloudnativepg.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [coreweave](<https://devfeed.tech/tags/coreweave.md>), [database](<https://devfeed.tech/tags/database.md>), [managed](<https://devfeed.tech/tags/managed.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>)

### AI overview

CoreWeave Database provides managed, PostgreSQL-compatible databases inside a CoreWeave Kubernetes Service (CKS) cluster, alongside AI workloads. Databases run on CPU nodes, store live data on CoreWeave Distributed File Storage, and use a primary with replicas across hosts for automatic failover. The service handles replication, patching, monitoring, and continuous backups, with point-in-time recovery within the retention window. Teams retain responsibility for data, schemas, queries, and database users; they control access through PostgreSQL roles and Kubernetes network policies. Connections use in-cluster endpoints, and the included pgvector extension supports embedding queries. The service uses CloudNativePG for PostgreSQL orchestration and adds CoreWeave console and Kubernetes workflows and managed storage and backups. The excerpt says existing PostgreSQL databases can be migrated using native tools, but gives no migration procedure or performance measurements.

### Source excerpt

CoreWeave Database is now generally available. Run managed PostgreSQL inside your CKS cluster, operated by CoreWeave, right next to your AI workloads.

## What LLMs do to PostgreSQL and DBAs

DevFeed: [What LLMs do to PostgreSQL and DBAs](<https://devfeed.tech/articles/what-llms-do-to-postgresql-and-dbas-126495.md>)

Original publisher: [Read original article](<https://www.depesz.com/2026/11/09/what-llms-do-to-postgresql-and-dbas/>)

Author: depesz

Published: 2026-11-09T20:54:04Z

Content type: opinion

Language: en

Sources: [select \* from depesz;](<https://devfeed.tech/sources/select-from-depesz.md>)

Topics: [Insight for DBAs](<https://devfeed.tech/topics/insight-for-dbas.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [bug-reports](<https://devfeed.tech/tags/bug-reports.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [community](<https://devfeed.tech/tags/community.md>), [discord](<https://devfeed.tech/tags/discord.md>), [explain](<https://devfeed.tech/tags/explain.md>), [explain-depesz-com](<https://devfeed.tech/tags/explain-depesz-com.md>), [irc](<https://devfeed.tech/tags/irc.md>), [list](<https://devfeed.tech/tags/list.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llms](<https://devfeed.tech/tags/llms.md>), [mailing](<https://devfeed.tech/tags/mailing.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [postgresql-19](<https://devfeed.tech/tags/postgresql-19.md>), [query](<https://devfeed.tech/tags/query.md>), [slack](<https://devfeed.tech/tags/slack.md>), [stats](<https://devfeed.tech/tags/stats.md>), [traffic](<https://devfeed.tech/tags/traffic.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>)

### AI overview

The author observes stable weekly traffic on pgsql-hackers, a rise in PostgreSQL bug reports beginning between May and September and increasing notably from mid-July 2026, and fewer messages on pgsql-general. They attribute these shifts, tentatively, to LLMs helping people find bugs and answer questions, alongside declines in Slack, Discord, and IRC activity. They also report less traffic to explain.depesz.com, suggesting people may increasingly trust machines to optimize queries without reading query plans themselves. The author presents this as a rapid, potentially worrying change, while leaving its value open to judgment.

### Source excerpt

Recently there has been some discussion about why so many features got reverted from PostgreSQL 19. I've read blogposts, talked with people, spent some time thinking. And it got me curious. I noticed lately that there is more mails to pgsql-bugs mailing list - basically reports of bugs, or conversations about them. I also noticed ... Continue reading "What LLMs do to PostgreSQL and DBAs"

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