News Roundup: June 12, 2026: Stack Overflow, pgEdge, GitLab longisland-ny.com/2026/06/12… #LONGISLAND

Stack Overflow has released into beta Stack Overflow for Agents, a knowledge exchange bult for the AI era. Autonomous agents are showing up all through workflows and the SDLC, yet are prone to hallucinating… dlvr.it/TT1Hr8 #AI #StackOverflow #GitLab #pgEdge #TechNews

News Roundup: June 12, 2026: #StackOverflow, #pgEdge, #GitLab securitytc.com/TT1Hqv

We ship code, not surveys. But here's one anyway, as we want to know your thoughts. What pgEdge repos are you using right now? (Spock, the AI DBA Workbench, the MCP server for Postgres, pgedge-vectorizer, pgedge-docloader, pgedge-anonymizer... there's a lot in the org now.) What made you reach for it? What have you yelled at your screen about? What would you put on the roadmap if you could? Drop it in the comments. We read them. Curious what you're building. And if there's something in our stack you're using or watching - star it. It's how you stay ahead of what we're shipping: new features, bug fixes, and so much more. 🔗 hubs.la/Q04lc5Kd0 - all repos, pick your favorites #postgres #postgresql #opensource #pgedge #developer #database

SQL:2011 standardized temporal tables over a decade ago. Most databases moved on it fairly quickly. Postgres took its time. Postgres 19 is changing that, and Shaun Thomas breaks it all down in this week's PG Phriday. The old approach required btree_gist, hand-written exclusion constraints, and making your application responsible for every time-range split on update or delete. It worked. But Postgres didn't actually understand your data was temporal - it was just columns and an unusual index type. The new way: PRIMARY KEY (product_id, valid_at WITHOUT OVERLAPS) No extension. No exclusion constraint. Postgres handles overlap prevention natively. You also get FOR PORTION OF for partial-range updates and deletes - update a two-year price record for just one quarter and Postgres handles the row splitting automatically. And temporal foreign keys using the PERIOD keyword, where referenced records must fully cover the referencing row's entire validity period. System time isn't there yet - the docs acknowledge it and point to trigger-based emulation in the meantime. But application-time is a meaningful step. Hetti Dombrovskaya and others have been making the case for this since 2015 through pg_bitemporal... now it's in core. ✨ Read the full article: 🔗 hubs.la/Q04lcrqD0 #PostgreSQL #Postgres #TemporalTables #SQL #DatabaseEngineering #pgEdge #OpenSource #Tech #TechNews

Your AI agent needs enterprise-grade, always-on Postgres. Your developers need infrastructure to build agentic workflows on it. Your team needs to know what's wrong at 3am when the agent's query patterns become the incident. Three different problems - and pgEdge ships for all three.  The pgEdge Agentic AI Toolkit is the infrastructure layer for building agents on Postgres: MCP Server for secure, structured schema and data access; RAG Server for retrieval; vectorizer for automatic background embedding generation as your data changes. No separate vector database. Builds on the Postgres you already run.  The pgEdge AI DBA Workbench is the operations layer. It monitors any PostgreSQL 14 instance - Amazon RDS, Supabase, pgEdge Cloud, community Postgres - with three-tier anomaly detection: z-score baselines, pgvector similarity against historical patterns, and LLM classification for what the first two tiers can't resolve. Ellie (an optional AI agent) runs diagnostics and walks through fixes step by step. You review and approve.  The Workbench MCP server also exposes the full tool catalogue to Claude Code, Cursor, and Windsurf directly - same diagnostics, from your IDE.  For the Postgres itself: pgEdge Enterprise Postgres - same-day patches, zero-downtime major version upgrades, enterprise-grade security, and active-active multi-master replication for any topology from single-region HA to write-anywhere global.  All three are free, open source, PostgreSQL License.  Explore the Agentic AI Toolkit: 🛠️ hubs.la/Q04l9-jN0 Read Dave's Workbench walkthrough: 📖 hubs.la/Q04l9yhw0 pgEdge Enterprise Postgres: 🔗 hubs.la/Q04lbsl30 #postgresql #postgres #dba #database #mcp #modelcontextprotocol #opensource #aiagents #devtools #claudecode #cursor #highavailability

"How does the model know the difference between a healthy pg_stat_activity snapshot on a quiet Tuesday and a runaway transaction on a Black Friday morning?" That's the question Dave Page has been trying to answer while building the pgEdge AI DBA Workbench. The Workbench is now generally available, and Dave published a technical deep-dive on how it actually works. The architecture: four services on a shared Postgres datastore. Ellie, the AI agent inside it, is an agentic loop that drives any LLM - Claude, OpenAI, Gemini, Ollama, or anything OpenAI-compatible - through a fixed set of database-aware tool calls. The model never queries your database directly. That's not a limitation. That's the design. Anomaly detection runs three tiers: z-score baselines catch the obvious deviations cheaply. pgvector similarity search flags patterns that match previous anomalies before they cascade. LLM escalation handles only what the cheaper tiers can't classify. Metrics, baselines, and alert history are stored in Postgres tables you can SELECT from yourself. One detail for the MCP crowd: the Workbench MCP server exposes its full tool catalogue to any HTTP MCP-compatible client. Claude Code, Cursor, VS Code Copilot, and Windsurf can connect directly and run the same diagnostics from your IDE - no Ellie required. Works on any PostgreSQL 14 : Amazon RDS, Supabase, pgEdge Cloud, or community Postgres. Free, open source, PostgreSQL License. Read Dave's walkthrough: 📖 hubs.la/Q04l2R6_0 #postgresql #postgres #dba #database #mcp #modelcontextprotocol #opensource #aiagents #devtools #claudecode #cursor #newrelease #tech #technews

You've got an AI app working on Postgres. Now what? Security hardening. Verifiable grounding. Token efficiency. Data sovereignty. These are the decisions that separate demos from production deployments. Next Thursday at 1PM ET, Mike Josephson (VP of Solutions Engineering, pgEdge) joins the PostgresWorld Webinar Series to walk through the solution that addresses each one: the pgEdge Agentic AI Toolkit, a collection of open source tools for building AI applications on any Postgres 14 . What he'll cover: 🔌 pgEdge MCP Server: full-featured MCP Server for controlled LLM access to any Postgres database, greenfield or pre-existing. Works with any MCP-compatible client. 💬 Natural Language Agents: CLI and web UI, both written in Go. Anthropic prompt caching cuts token costs by 90%. 🧩 pgEdge-vectorizer: a Postgres extension that auto-chunks your text and generates embeddings via background workers. Supports OpenAI, Voyage AI, and Ollama. 📡 pgEdge RAG Server: dedicated HTTP API for retrieval-augmented generation with hybrid search (vector BM25), token budget management, and streaming. The same stack that powers Ellie (an optional AI assistant) running live on hubs.la/Q04kYSK30. 📥 pgEdge-docloader: converts HTML, Markdown, RST, or SGML docs into Postgres-ready content. The on-ramp for your RAG pipeline. 🔍 VectorChord-bm25: BM25 ranked search for Postgres, for hybrid semantic and full-text retrieval. All pgEdge components are 100% open source under the PostgreSQL license. Your data stays in Postgres: no external vector store, no proprietary pipelines. Free to attend, or register now and get the recording later. 🎙️ hubs.la/Q04kYy2_0 #postgres #postgresql #ai #mcp #modelcontextprotocol #rag #vectorsearch #llm #opensource #pgedge #webinar #database

PgDay Boston wrapped up yesterday at the Museum of Science, and it was a solid event. The pgEdge team was there for a full day of community Postgres talks, and the presentations were genuinely good. Michael Stonebraker keynoted.  A strong first for the Boston Postgres community. 🐘 #pgdayboston #postgresql #postgres #boston #database #opensource #community

Most enterprise AI projects don't stall because the model is wrong. They stall because the database behind the application can't meet the requirements of production. pgEdge CEO David Mitchell breaks down why agentic AI makes this problem more urgent, not less. Agentic systems aren't just answering questions anymore; they're retrieving live data, initiating actions, updating records, and reasoning across systems in real time. That's a different set of requirements than most enterprise data environments were built to handle. His piece for RT Insights: 📖 hubs.la/Q04kS0bZ0 #agenticai #enterpriseai #ai #database #postgresql #postgres #data #datainfrastructure

The pgEdge AI DBA Workbench works on any Postgres 14 : managed cloud, self-hosted, on-premises, or fully air-gapped. No agents on your nodes. No migration. Nothing changes in how your database runs today. Paul Rothrock has walkthrough videos for five managed setups, in case you are using any of them: 1. Amazon RDS: full SSL cert setup, scraping your RDS or Aurora instance 🔐 hubs.la/Q04kwPdT0 2. Supabase: Session Pooler connection, Ellie analyzing real workload data 🔌 hubs.la/Q04kwrfq0 3. AlloyDB: deep Postgres observability layered on top of a managed database 🔍 hubs.la/Q04kwRjS0 4. Azure Flexible Server: firewall rules, pg_stat_statements, and why not to use Entra ID tokens for a long-running collector ⚙️ hubs.la/Q04kwnQ50 5. Citus: treating your coordinator and worker nodes as one distributed cluster, not separate servers 🗺️ hubs.la/Q04kwP_C0 Not sure what the Workbench does yet? Start here: hubs.la/Q04kwtGP0 🐘 Free. Open source. PostgreSQL License. #postgresql #postgres #dba #monitoring #opensource #aws #azure #supabase #alloydb #citus

The pgEdge Control Plane just shipped two features that go in opposite directions on purpose. 🧩 Supporting Services (fully available): your database and the services around it (MCP Server, RAG Server, PostgREST) now live in the same declarative spec. One JSON, one POST, and the Control Plane provisions everything together with scoped, auto-rotated credentials per service. Co-locate them with database nodes for low latency, or split them onto dedicated hosts. 🐧 systemd Support (Preview): the Docker Swarm requirement that was blocking regulated-industry teams is gone. Run the Control Plane and Postgres as systemd units on standard OS paths. Same declarative API as the container path. RHEL beta is live, Debian to follow. What ties them together: the API doesn't change. Same spec creates a multi-master Spock cluster on Docker Swarm or directly on the host via systemd. Same spec adds an MCP server next to a primary or PostgREST instances at every node. Your CI/CD doesn't care which orchestrator runs underneath. Antony Pegg's full write-up has the JSON example with more details: 📖 hubs.la/Q04f-FJ40 #postgres #postgresql #devops #systemd #databases #opensource #infrastructure #postgresprofessionals #linux #programming #docker

pgEdge Control Plane: a lightweight orchestrator for PostgreSQL. Declare the database you want in JSON, POST it, and Control Plane handles configuration, multi-master replication via Spock, HA via Patroni, and backups via pgBackRest. 🐘 Highlights: 🌍 Multi-region active-active deployments ⚡ Zero-downtime node addition on running clusters 💾 Declarative pgBackRest backups, point-in-time restores 🔄 Switchover, failover, and scaling through one API 🧩 Postgres 16, 17, 18 with Spock, pgVector, PostGIS, pgAudit, and more Open source under the PostgreSQL License. ⭐ hubs.la/Q04fxmdm0 #postgres #postgresql #devops #databases #opensource #k8s #kubernetes #containers #docker

五一发布了一个新版本 Pigsty v4.3，这次搞来了 50 个新的 PG 扩展，总数达到了 510 个，基本上覆盖了 PG 生态里所有“能打”的扩展。还支持了刚发布的 Ubuntu 26.04，并更新了 Supabase，pgEdge，OrioleDB，PolarDB 几个内核。另外 Github Star 破了 5000，文档站月 PV 过亿，算是到了一个新里程碑吧。 vonng.com/pigsty/v4.3/

Pigsty v4.3 released with 50 new extensions (510 in total!), and support for Ubuntu 26.04 resoulte. We also update supabase, pgEdge (17 -> 18), orioledb (beta15), polardb (15->17) and other infra packages, check release note for details. vonng.com/en/pigsty/v4.3/

Learn why developers choose Postgres for AI. See how pgvector and structured data provide the ground truth for reliable AI apps. Thanks to pgEdge thenewstack.io/postgres-ai-g…

Today we're announcing the pgEdge AI DBA Workbench: an open source co-pilot for Postgres teams that are managing more databases, across more regions, with the same number of people they had two years ago. It continuously monitors query performance, replication health, vacuum activity, connection counts, WAL throughput, and more across your entire Postgres estate. When something looks wrong, it doesn't just fire an alert and leave you to figure out the rest. Ellie, the built-in AI agent, investigates, walks you through the diagnosis step by step, and gives you the exact SQL to fix it. You decide whether to run it. Built by the team behind pgAdmin, the most widely used open source Postgres management tool in the world. Works with any Postgres 14 instance, and fully open source under the PostgreSQL License. 🐘 Read the full announcement below. 🔗 hubs.la/Q04d1Vyb0 #postgresql #postgres #dba #monitoring #ai #opensource #technews #data #programming #sql