🚨 UPDATE — Splunk CVE-2026-20253: A public PoC is now on GitHub. No confirmed exploitation yet — but that window is closing fast. Critical detail many admins are missing: the PostgreSQL sidecar is active by default on Splunk Enterprise deployed on AWS — making cloud deployments exposed out of the box. Also confirmed: a second high-severity RCE (CVE-2026-20251, CVSS 8.8) in the same patch batch hits the Splunk Secure Gateway via unsafe Python deserialization — low-privileged user, no admin needed. Patch to 10.0.7, 10.2.4, 9.4.12, or 9.3.13. Don't wait. 👇 thehackernews.com/2026/06/cr…

EXPLAIN visualizer in @PostgreSQL extension for @code - which view do you prefer? Tree, Icicle, or Table?

CREATE TABLEなどのSQLからER図を自動生成。ブラウザで試せるデモあり。セルフホストも可能。PostgreSQL/MySQL/SQLite/MSSQLに対応。pngやsvgでエクスポートも可。 / “GitHub - royalbhati/sqltoerdiagram: ER diagram generator. Paste CREATE TABLE statements and get a…” htn.to/2VQ6kbqwUC

By forking PostgreSQL and embedding triple-entry accounting BSV tokenisation directly into the database engine, the system can: Ingest real invoices and shipping documents automatically Record them as cryptographically verifiable triple-entry entries Tokenise them on BSV Provide proofs that everything balances and is auditable Integrate with the rest of the ecosystem (payments, access control, NFTs) github.com/prof-faustus/trip…

🚨 NEW: CVE-2026-20253 (CVSS 9.8) — unauthenticated RCE in Splunk Enterprise. A PostgreSQL sidecar endpoint has zero authentication controls, letting any network-reachable attacker create or truncate arbitrary files — and chain that into full remote code execution by overwriting Python scripts Splunk runs automatically. watchTowr just dropped a full technical walkthrough. No exploitation confirmed yet — but the attack chain is now fully public. Splunk Enterprise 10.4 is safe. Fix: patch to 10.0.7 or 10.2.4. Splunk Cloud is not affected. If Splunk is your SIEM — patch immediately. Full breakdown 👇 thehackernews.com/2026/06/cr…

Critical Splunk Enterprise Flaw Lets Attackers Run Code Without Authentication cysecurity.news/2026/06/crit… #PostgreSQL #RCE #Splunk

WEEKLY UPDATE This week I: Got a take-home assignment from a startup and completed it before the deadline. Built a customer support chatbot using: → Svelte (learned Svelte while building it) → Node.js → PostgreSQL → Redis → OpenAI

Nobody wanted PostgreSQL in 1994. Now nobody can live without it. In 1986 Professor Michael Stonebraker at UC Berkeley spent eight years building a database called POSTGRES. Funded by DARPA. Dozens of papers. A team of brilliant students. Then Berkeley shut it down in 1994. Too much maintenance. Not enough research value. The code was left on a server and forgotten. Two graduate students named Andrew Yu and Jolly Chen were not ready to let it die. They took the abandoned code, added SQL support and released it to the world for free. No funding. Just two students who believed the database was worth saving. They called it Postgres95. Two years later it was renamed PostgreSQL. A global community of volunteers took it from there and never stopped. Today PostgreSQL is the most advanced open source database on earth. Notion runs on it. Shopify runs on it. Instagram was built on it. Apple uses it internally. Amazon built Aurora PostgreSQL because their customers demanded it. Companies built on a PostgreSQL base have generated over $2.6 billion in acquisitions. Stonebraker won the Turing Award in 2014. The Nobel Prize of computer science. Partly for the database his own university threw away. Oracle charges enterprises hundreds of thousands of dollars a year for what two grad students rescued from a forgotten server and gave away for free. Some things are too important to let die.

I was building a full-stack accounting system dual-entity, retail and wholesale, with a PostgreSQL layer, journal templates, bank account selectors, void logic, the works. At one point the AI built something that genuinely worked. Not just compiled. Not just passed tests.

Built Dolearnnn, a full stack marketplace with scheduling, payments, notifications, and workflow automation. TypeScript, React, Next.js, Node.js, PostgreSQL. Dolearnn.com

LunarisSec uncovered a critical vulnerability affecting crqxx.gov.br. A Broken Access Control flaw allowed extraction of two database dumps (PostgreSQL >2MB and MySQL >7MB), including 38 tables, schemas, SQL data, plaintext credentials, and admin SHA-1 hash.

Managing a PostgreSQL cluster with raw Pods is like making coffee by hand in an office breakroom.👇 Find the mug. Boil water. Measure grounds. Pour milk. Clean up. Miss one step — the whole thing burns. The Kubernetes Operator Pattern is the smart vending machine. You press one button. The machine handles everything else — and if the milk runs low mid-pour, it self-corrects. That button is your CRD. That machine is your Custom Controller. #Kubernetes #DevOps #Platform #SRE

Azure announces the general availability of SQL MCP Server, delivering secure, high-performance solutions compatible with SQL and PostgreSQL. Ideal for modern workloads requiring scalability and reliability. #NerdieCloud #CloudNews #CloudUpdates #Azure #Microsoft #Kubernetes

Over the last 30 days, I built: ✅ Patient Appointment Booking ✅ Appointment Tracking with Booking Codes ✅ Search & Filtering ✅ Admin Dashboard ✅ Staff Management Module ✅ Role-Based Authentication ✅ Staff Activation/Deactivation ✅ PostgreSQL Database Integration

For most production workloads today: PostgreSQL pgvector first. I only reach for dedicated vector databases when scale or retrieval requirements justify the extra complexity.

I have 2 small projects and they have just a little of traffic Together they cost me ~6$ where Deep Prep runs: - web worker - async worker - postgreSQL - redis

✅To avoid lock-stealing, lock release is handled through an atomic Lua script that verifies ownership before deletion ✅PGSQL pessimistic row locks act as a second layer of protection during booking confirmation. #Backend #SystemDesign #Redis #PostgreSQL #NestJS #BuildInPublic

PostgreSQL

Today I ran into a real challenge while building my EcoHope POS system with Django. PostgreSQL refused to connect, migrations failed, and I had to debug step by step. But that’s the process — every error is part of understanding how real systems work. Still building, still learning. #Python #Django #BuildInPublic #Programming