pg-jev is a PostgreSQL extension that wraps TypeSafe's Jev library into SQL functions, enabling semantic classification, probability scoring, and label selection directly in queries without vector indexes or embeddings, with performance benchmarks and operational caveats.
The article introduces AIHOT, an open-source AI-powered news aggregation system that automatically collects, filters, scores, clusters, and publishes daily briefings; its methodology (prompts, scoring, thresholds) is fully open, allowing anyone to adapt it to their industry by changing sources and calibration data.
The article details how a SaaS team evolved a fragile LLM ticket-classification script into a production-grade pipeline using strict Pydantic contracts, PostgreSQL state machines with atomic leasing, Kafka outbox patterns, immutable training snapshots, and metric-gated rollouts to handle model drift, replay, and human review safely.
In an 80-minute interview, Turing Award winner Mike Stonebraker argues that relational databases will absorb AI workloads, explains why Text-to-SQL fails on real enterprise data due to schema corruption and access controls, details DBOS's persistent workflow approach for AI agents, and discusses saga patterns for compensating transactions, graph database limitations, and the future of open-source AI.
This article benchmarks PostgreSQL JSON and JSONB types on 1 million rows, revealing JSONB delivers 6-9x faster queries and 26% less storage despite 31% slower writes, with practical guidance on when to choose each type and how to leverage GIN indexes for optimal performance.
The author benchmarks MariaDB 10.3, MySQL 8.0, and PostgreSQL 12 using a real Turkish motorcycle classifieds app with many simple queries, finding MariaDB 5% faster on average and 7% faster at p95 with lower CPU usage, though MySQL handles tail latency better and memory differences stem from default performance_schema settings.
This comprehensive guide covers MySQL and PostgreSQL monitoring essentials, including key metrics (connections, throughput, InnoDB, replication), version-specific differences, alert thresholds, exporter deployment (mysqld_exporter, postgres_exporter), Grafana dashboards, Prometheus alerting rules, troubleshooting playbooks for common issues like connection exhaustion, replication lag, deadlocks, and disk growth, plus automation scripts for long-transaction killing and slow-query analysis.
This article demonstrates how PostgreSQL's JSONB type combined with Spring Boot provides a practical alternative to MongoDB for managing dynamic custom fields in enterprise applications, covering storage, indexing, JPA mapping, partial updates, querying patterns, and performance tuning while preserving relational integrity.
Scott reflects on 17 years and six DTCC talks, tracing his evolution from database user to builder to data-centric innovator, sharing a career framework (I→T→π) and four self-assessment questions to align skills with market shifts like cloud, AI, and semantic storage.
This article introduces a production-ready Go Gin DDD scaffold featuring four-layer architecture, RocketMQ event-driven messaging, dual MySQL/PostgreSQL databases, unified responses, and step-by-step guides for setup and new module development.
This article compares PostgreSQL and MySQL across complex query optimization, data types, MVCC implementation, transaction rollback capabilities, and cloud ecosystem support, explaining why PostgreSQL is increasingly preferred for complex analytics, vector search, and geospatial applications.
The article chronicles the twelve‑year evolution of China’s Database Technology Conference (DTCC), showing how it transformed isolated DBA communities into a collaborative ecosystem, introduced new topics such as cloud and NoSQL, and enabled figures like 那海蓝蓝 to shape the nation’s database engineering landscape.
InsForge is an open‑source backend platform that bundles PostgreSQL, authentication, object storage, serverless functions, real‑time messaging and a unified model gateway, exposing them via MCP so AI coding agents like Cursor and Claude can automatically provision, configure and deploy full‑stack services with a single command.
This article details how to turn ontology‑based semantic assets into a runnable Semantic Service that answers risk queries and suggests actions, using a three‑layer architecture of deterministic code, a versioned knowledge base, and LLM‑driven reasoning, illustrated with a customer health‑score example.
This guide walks through the complete process of designing, configuring, and operating a PostgreSQL primary‑standby setup with streaming replication, choosing between asynchronous and synchronous modes, implementing read‑write splitting via application routing or PgBouncer, and handling monitoring, failover, and common pitfalls for production‑grade high availability.
This article walks through a systematic approach to sizing PostgreSQL connection pools for Java applications using HikariCP and Spring Boot, covering capacity budgeting, workload‑driven calculations, monitoring metrics, slow‑SQL analysis, leak detection, Kubernetes deployment considerations, and safe rollout practices.
An interview story reveals that storing embeddings in MySQL forces a full‑table scan, leading to second‑level latency, while production‑grade RAG requires a vector database with ANN indexing such as HNSW or IVFFLAT, offering millisecond response, high recall, and scalable storage.
This article walks MySQL developers through the essential architectural, schema, data‑type, SQL‑dialect, transaction, vacuum, indexing, and extension differences when moving to PostgreSQL, providing concrete examples, code snippets, and best‑practice recommendations to avoid common pitfalls.
The article provides a comprehensive PostgreSQL operational self‑checklist covering CPU, memory, generic plans, idle connections, autovacuum, checkpoint and bgwriter tuning, AI workload handling, index building, replication, migration, partition management, and observability, with concrete examples, benchmarks, and practical commands.
In a SaaS analytics platform with a 45‑billion‑row, 1.2 TB events table, the author shows how moving to native PostgreSQL range partitioning by event_time, combined with zero‑downtime migration steps, reduced the typical P99 query latency from 43 seconds to about 0.3 seconds while enabling easier data lifecycle management.
PostgreSQL is attracting renewed interest not because it magically becomes an all‑purpose AI database, but because AI applications in production demand a unified, consistent platform that can manage business records, vector embeddings, agent state, permissions and tooling, and PostgreSQL’s extensible ecosystem—pgvector, serverless architectures, branching, and MCP—offers exactly that blend of relational reliability and AI‑native capabilities.
In PostgreSQL versions prior to 14, a DELETE without a partition filter on a table with 20,000 partitions caused the server to allocate over 120 GB of memory within 60 seconds; the article shows how to reproduce the issue, diagnose it with MemoryContextStat and perf, and explains the fix introduced in PG14.
The article examines how databases, after five decades of human‑centric design, are undergoing a fundamental transformation driven by Agentic AI, requiring new semantics, multimodal storage, memory capabilities, and integrated engines, illustrated through insights from Yang Yu of KuKe Data.
This article explains how to capture and stream row‑level changes from PostgreSQL using its Write‑Ahead Log, compares the approach with MySQL binlog CDC, and provides a step‑by‑step guide—including configuration, logical decoding, snapshot handling, replication slots, and production‑grade correctness considerations—to build a reliable CDC pipeline.
The article dissects CVE-2026-57588, a high‑severity SQL injection in Tenable Nessus 10.12.0 and earlier, explaining how malicious .nessus XML files can execute arbitrary PostgreSQL queries when imported by an administrator, and provides remediation steps and a PoC script.
Databasus is an open‑source backup management platform that unifies PostgreSQL, MySQL, MariaDB and MongoDB backups with a web UI, offering logical, physical and incremental backups, automated scheduling, AES‑256‑GCM encryption, multi‑cloud storage, RBAC collaboration, and optional agents for secure, out‑bound connections.
In a candid interview, PostgreSQL founder Michael Stonebraker recounts his journey from Ingres to Postgres, critiques Oracle’s sales tactics, denounces Google’s and Amazon’s database strategies, explains Postgres’s extensible type system, explores the DBOS research project, and highlights why current large‑language‑model‑to‑SQL solutions remain far from production‑ready.
The pgrust project rewrites PostgreSQL's core in Rust, passes all 46,066 official regression tests, supports standard SQL and the psql client, but remains experimental, exploring a thread‑per‑connection model and showcasing how AI‑driven coding can lower the cost of large‑scale infrastructure rewrites.
This article provides an in‑depth analysis of PostgreSQL's lock system, covering lock types, MVCC interaction, deadlock detection, advisory locks, monitoring scripts, and practical optimization techniques for production environments.
The article explains how AI‑generated code can be delivered in seconds, but traditional databases add a ten‑minute bottleneck, and shows that Volcano Cloud PostgreSQL Serverless reduces instance creation to 10 seconds, speeds up branch operations 200‑fold, offers scale‑to‑zero, cuts costs by 99.99%, and provides a Data‑as‑Git workflow with a step‑by‑step recovery demo.
This article walks through switching a SpringBoot + MybatisPlus project from MySQL to PostgreSQL, covering driver addition, JDBC URL changes, schema differences, and a detailed list of SQL syntax mismatches and runtime errors with concrete code examples and remediation scripts.
The article re‑examines SQLite’s historic reputation as a test‑only database, showing how SSD‑backed WAL mode, tools like LibSQL/Turso, Litestream, and Cloudflare D1, plus modern JVM support, give SQLite production‑grade performance for read‑intensive, multi‑tenant and edge scenarios, while outlining when PostgreSQL remains necessary.
The article compares four emerging data‑lake‑for‑PostgreSQL solutions—Databricks LTAP, EDB Fusion Analytics, Snowflake pg_lake, and pgEdge's ColdFront—highlighting ColdFront's unique transparent Iceberg layer, writable cold data, DuckDB integration, and the strategic trade‑offs developers must weigh when choosing a modern OLTP/OLAP/AI architecture.
This article provides a comprehensive, enterprise‑level comparison of PostgreSQL and MongoDB, outlining when each database fits business needs, a five‑dimensional decision framework, mixed‑architecture patterns, practical schema and indexing examples, and guidance on performance, stability, and migration considerations.
This comprehensive guide walks through PostgreSQL's backup and replication architecture, explaining WAL fundamentals, the distinction between backup, high‑availability, disaster‑recovery and CDC, and provides step‑by‑step configurations, performance trade‑offs, monitoring queries, Kubernetes deployment tips, and practical recovery‑drill procedures for production environments.
The article explains how to self‑host Multica using a three‑container Docker Compose setup—PostgreSQL, backend, and frontend—detailing secure defaults, health‑checked service dependencies, advisory‑lock‑based migrations, loopback port bindings, and two launch methods (official images or local builds) that let you start the system with just three commands.
This article dissects PostgreSQL's Write‑Ahead Logging (WAL), explaining how it underpins transaction durability, replication, CDC, point‑in‑time recovery, and commit latency, and provides a step‑by‑step guide to architecture design, parameter tuning, troubleshooting, containerization, backup strategies, and operational checklists for production‑grade deployments.
The article analyzes how reliance on AI coding assistants erodes developers' hands‑on skills, compares this to aviation automation bias, and proposes a “mixed‑intelligence” approach that balances AI efficiency with deliberate manual practice to retain low‑level control and resilience.
The article dissects GBrain, an open‑source AI memory engine from Y Combinator’s Garry Tan, showing how a dual‑engine contract, zero‑LLM regex‑based knowledge‑graph extraction, and a layered hybrid retrieval pipeline boost P@5 from ~18 to 49.1 while detailing engineering trade‑offs, batch‑write work‑arounds, weighting constants, and reliability mechanisms.
The article analyzes common mistakes when moving from MySQL to PostgreSQL—such as oversized connection pools, blind max_connections tweaks, oversized transactions, idle‑in‑transaction connections, and indiscriminate indexing—and offers concrete, step‑by‑step guidance to achieve a stable, well‑tuned PostgreSQL deployment.
This comprehensive guide compares PostgreSQL and MySQL from an engineering perspective, covering business models, transaction semantics, concurrency, replication, scalability, operational costs, real‑world case studies, and a decision matrix to help teams choose the database that minimizes long‑term complexity and cost.
The article explains why developers should move beyond MySQL to PostgreSQL, illustrating the productivity gains of native window functions, MVCC concurrency, rich indexing, JSONB support, and extensive extensions through detailed examples, installation guides, performance comparisons, and real‑world use cases.
This guide shows how to install, configure, and manage MySQL/MariaDB, Redis, and PostgreSQL inside Windows Subsystem for Linux, including remote access setup, common command‑line operations, GUI client recommendations, and scripts for one‑click start/stop and backup.
Even with 2 TB of RAM, PostgreSQL can hit OOM because work_mem is a per‑operation budget that multiplies across sorts, hashes, parallel workers and long‑lived memory contexts, so blindly raising it often hides deeper query‑design and statistics issues.
The article explains why many developers stuck with MySQL should consider PostgreSQL, highlighting its superior SQL standards support, MVCC concurrency, rich indexing, JSONB performance, full‑text search, extensive extensions, and practical installation and Java integration steps, while also comparing pros, cons, and ideal use cases.
In a high‑concurrency transaction system, the author diagnosed a 30‑second API latency caused by costly SQL scans and Java Map creation on over two million rows, then applied SQL aggregation, moved counting logic into PostgreSQL, and introduced a Caffeine cache, ultimately reducing the response time to under 0.8 seconds while highlighting relational‑database limits for massive data.
This article walks you through installing PostgreSQL via binary packages or source compilation, securing the instance, and applying memory, connection, and WAL tweaks on a 16‑core, 32 GB server to boost throughput from under 1 k TPS to over 4 k TPS.
This article showcases a collection of impressive SQL queries—including a PostgreSQL Tetris implemented with a recursive CTE, window‑function session analysis, a ClickHouse real‑time funnel, dynamic WHERE clause generation, and a recursive employee hierarchy—while discussing performance tips and engine choices.
The article explains why increasing PostgreSQL's work_mem does not guarantee per‑query memory limits, how multiple sort/hash nodes, parallel workers and long‑lived memory contexts can cause OOM even on a 2 TB server, and offers concrete diagnostics and mitigation strategies for DBAs and developers.
The article questions whether dedicated vector databases are truly needed for AI applications, examining market hype, the rapid emergence of many vector‑DB products, real‑world examples like PostgreSQL pgvector and major vendor integrations, and the hidden costs of data fragmentation and operational complexity.
This article explains why naïve database‑per‑tenant designs cause resource waste and operational headaches, and demonstrates how Spring Boot, Hibernate, and PostgreSQL schemas provide a lightweight, high‑performance multi‑tenant architecture with strong isolation, low overhead, and easy scalability.
An AI‑driven security tool discovered high‑severity, remote‑code‑execution flaws in PostgreSQL's pgcrypto extension and MariaDB's JSON schema validation, both dating back over two decades, prompting immediate patch releases and offering mitigation steps for unpatched deployments.
The article compares PostgreSQL and MySQL, highlighting PostgreSQL's richer data types, extensible ecosystem, advanced replication and monitoring features, while exposing MySQL's limitations in data modeling, sequence support, tooling, and replication, and concludes that the best choice depends on specific workload requirements.
The php.internals vote on April 4 approved moving PHP 9.0 to the permissive 3‑clause BSD license, replacing the dual PHP v3.01 and Zend Engine licenses, and the article explains the historical reasons, legal benefits, comparisons with other BSD variants, PostgreSQL’s approach, and broader open‑source licensing trends.
The article argues that relying on many specialized databases creates operational complexity, higher costs, and maintenance overhead, while PostgreSQL’s extensible ecosystem—offering full‑text search, vector, time‑series, JSONB, and more—delivers comparable or superior algorithms, proven performance, and a simpler, more reliable stack for the vast majority of use cases, especially in AI applications.
The article compares PostgreSQL and MySQL across data types, native sequences, extensions, monitoring tools, replication mechanisms, licensing, community governance, and MVCC implementation, showing why many Chinese tech giants favor PostgreSQL for complex, high‑consistency workloads while acknowledging MySQL’s strengths in simple web scenarios.
PostgreSQL’s extensible architecture lets it evolve from a relational DB into a true multi‑model system supporting graphs, vectors, full‑text, time‑series, GIS and key‑value data, with detailed architecture explanations, practical code demos, cross‑model queries, extension selection, and production‑grade best‑practice tips.
The article explains why RAG storage must be layered, describes the four data types involved, presents a typical three‑layer architecture with vector, content, and metadata stores, and shows how the design evolves with scale, multi‑level indexing, update handling, and tenant isolation.
This tutorial extends the previous FastAPI example by adding Redis caching and Celery asynchronous tasks, showing the project layout, a complete docker‑compose configuration, required Python packages, sample FastAPI and Celery worker code, startup commands, health‑check setup, and key takeaways.
When a core order‑query suddenly slowed from milliseconds to seconds, the team discovered that using PostgreSQL’s EXPLAIN ANALYZE revealed hidden plan regressions, outdated statistics, and index misuse, leading to a systematic, production‑grade methodology for diagnosing and fixing query performance issues.
This article examines how PostgreSQL can take over Redis' roles—caching, pub/sub, and job queues—by leveraging unlogged tables, LISTEN/NOTIFY, and SKIP LOCKED, presenting cost savings, benchmark results, migration steps, and code examples for a practical backend replacement.
TimescaleDB 2.26.2 focuses on fixing high‑impact bugs—continuous aggregates errors, compression task crashes, and lock‑related deadlocks—while improving memory stability and PostgreSQL compatibility, and the article provides detailed upgrade instructions and best‑practice recommendations.
This article explains PostgreSQL's native full‑text search, its core concepts of tsvector and tsquery, demonstrates how to use built‑in functions and operators, compares built‑in, zhparser, and pg_search extensions for Chinese tokenization, and provides best‑practice tips for indexing, triggers, and performance optimization.
The article analyzes why many Chinese cloud providers and enterprises prefer PostgreSQL to MySQL, detailing PostgreSQL's richer data types, native sequence support, extensible ecosystem, advanced monitoring, robust replication, open licensing, and MVCC implementation, while acknowledging MySQL's remaining advantages in specific scenarios.
This article compares PostgreSQL and SQL Server data access methods—including sequential scans, index scans, bitmap heap scans, index‑only scans, and parallel query execution—highlighting PostgreSQL's lack of clustered indexes and the performance implications of each approach.
This comprehensive guide explores PostgreSQL 17's lock mechanisms, covering lock classifications, table‑ and row‑level lock behavior, MVCC interaction, common pitfalls such as deadlocks and lock contention, and provides practical SQL queries, Bash monitoring scripts, advisory‑lock techniques, and best‑practice recommendations for performance tuning and reliable production deployment.
Amid China's push for independent, cloud‑native databases, leading firms like Tencent, Alibaba, Huawei and others have built PostgreSQL‑based solutions, and this article analyzes why PostgreSQL’s richer data types, true sequence objects, extensible ecosystem, advanced replication and licensing advantages make it a preferred choice over MySQL.
In 2026 the database ecosystem faces fierce competition between MySQL and PostgreSQL, while AI emerges as a new driver prompting open‑source projects like AliSQL to release DuckDB, vector engines and intelligent CLI, reshaping how relational databases serve both transactional and analytical workloads.
This article explains how combining Go, PostgreSQL, and sqlc creates a Zero‑ORM architecture that restores SQL to the center of high‑performance, highly controllable, and maintainable backend services, covering design principles, layer responsibilities, schema and query patterns, connection‑pool tuning, transaction handling, observability, and practical best‑practice checklists.
The article explains how Gemini CLI’s shift from traditional Tools to progressive Agent Skills streamlines Cloud SQL for PostgreSQL extensions, reducing context overload, enabling on‑demand skill loading, zero‑manual installation, and cross‑platform execution, and provides step‑by‑step commands for exploring and using these new capabilities.
The article examines the sharp decline in MySQL’s commit activity since its 2006‑2007 peak, compares recent DB‑Engines rankings that show PostgreSQL overtaking MySQL, and attributes the downturn to Oracle’s management practices, technical setbacks, reduced open‑source community engagement, and a shift toward proprietary alternatives.
This guide explains how to set up Prometheus monitoring for PostgreSQL using the open‑source postgres_exporter, covering both single‑node Docker installation and multi‑node configuration with custom authentication files and Prometheus scrape settings.
This guide explains what PostgreSQL execution plans are, how they are generated, and how to interpret them using EXPLAIN and EXPLAIN ANALYZE, then demonstrates three real‑world case studies that show step‑by‑step optimizations with indexes, configuration tweaks, and query rewrites to dramatically improve query speed.
This comprehensive guide walks you through PostgreSQL 17 deployment, explains its multi‑process architecture and MVCC model, details environment requirements, shows essential configuration parameters, provides step‑by‑step backup and PITR procedures, demonstrates streaming replication setup, and shares best‑practice tuning, security, and monitoring tips for reliable production use.
A concise roundup of major AI developments on March 2, 2026, covering Palantir's stock surge linked to Anthropic tech in a US airstrike, OpenAI's controversial DoD agreement, breakthroughs in large‑model optimization, PostgreSQL scaling, competitive wins, new recommendation systems, open‑source model releases, and emerging research from top universities.
The article analyzes why many leading Chinese tech firms adopt PostgreSQL despite MySQL’s popularity, detailing PostgreSQL’s richer data types, native sequence support, extensible ecosystem, advanced monitoring tools, robust replication, open‑source licensing, and MVCC implementation, while also acknowledging MySQL’s strengths in simple deployment and read‑heavy workloads.
This guide explains the advantages of using PDO instead of mysqli for PHP database connections, walks through MySQL and PostgreSQL setup with detailed code examples, recommended configuration options, and a checklist for troubleshooting common connection errors.
The article presents a production‑grade, modular design methodology for payment domain systems, detailing five core modules, essential principles such as idempotency and ACID, concrete implementation examples with Kafka, Redis, PostgreSQL, and guidance on risk, compliance, and high‑availability engineering.
This guide introduces a collection of PostgreSQL SKILL scripts for automated health checks and operational analysis, explains the repository layout, shows how to run individual or full daily checks, lists all available skills, and provides a sample report with actionable recommendations.
The article examines why major Chinese cloud and technology providers are building distributed, cloud‑native or HTAP databases on PostgreSQL instead of MySQL, detailing differences in data types, sequences, extensions, monitoring, replication, licensing, and MVCC implementation.
Amid rising demand for open‑source, self‑controlled databases in China, major firms such as Tencent, Alibaba, and Huawei have built PostgreSQL‑based distributed, cloud‑native solutions, citing PostgreSQL’s richer data types, native sequence support, extensible ecosystem, advanced monitoring, robust replication, and true open‑source licensing as decisive advantages over MySQL.
In under a month the author migrated more than 100 heterogeneous tables from MySQL and MongoDB to PostgreSQL across isolated networks by automating Navicat's import/export logic, streaming data, handling special characters, configuring flexible sync strategies, and using OSS as a bridge to avoid OOM and lock‑contention.
The article reveals seven common PostgreSQL architectural oversights—such as neglecting vacuum, misusing UUID primary keys, treating the database as a queue, missing indexes, over‑relying on ORMs, ignoring write‑side scaling, and failing to partition large tables—that silently degrade performance and reliability, and provides concrete fixes and best‑practice configurations.
OpenAI’s engineering team expanded a single‑primary PostgreSQL cluster with nearly 50 read‑only replicas, migrated write‑heavy workloads to Azure Cosmos DB, and applied extensive optimizations to reliably serve the global traffic of ChatGPT and the OpenAI API for 800 million users at multi‑million queries per second.
This article compares PostgreSQL and MySQL, highlighting PostgreSQL's richer data types, native sequences, extensible ecosystem, advanced monitoring, robust replication, open licensing, and MVCC implementation, while also acknowledging MySQL's strengths in simplicity and read‑heavy web workloads.
OpenAI runs a single primary PostgreSQL with about 50 replicas to serve roughly 800 million ChatGPT users, employing PgBouncer connection pooling, cache‑lock mechanisms, query and schema optimizations, workload isolation, multi‑layer throttling, and cascade replication, while acknowledging the architecture’s limits and the complexity of full sharding.
The article debunks OpenAI's sensational claim of handling 800 million ChatGPT users with a single PostgreSQL instance, revealing a pragmatic hybrid architecture that combines many read replicas, Azure CosmosDB for write‑heavy workloads, and top‑tier hardware, while highlighting cost and complexity considerations.
The article compares PostgreSQL and MySQL, detailing PostgreSQL’s richer data types, true sequence support, extensible ecosystem, advanced monitoring and replication features, while also acknowledging MySQL’s simplicity and strong points, to help readers decide which database fits their workload best.
The article examines why major Chinese cloud providers and enterprises are building PostgreSQL‑based distributed, cloud‑native databases instead of MySQL, detailing PostgreSQL's richer data types, native sequence support, extensible ecosystem, advanced replication, licensing advantages, and MVCC implementation, while also noting MySQL's remaining strengths.
This guide enumerates frequent misconceptions in SQL performance—from over‑indexing and SELECT * misuse to improper transaction handling and outdated monitoring practices—explains why they hurt efficiency, and provides concrete, version‑aware solutions to optimize queries, schema design, and database operations.
The article compares PostgreSQL and MySQL, highlighting PostgreSQL's richer data types, true sequence support, powerful extensions, built‑in monitoring, advanced replication, open‑source licensing, and MVCC implementation, while acknowledging MySQL's strengths in quick deployment and read‑heavy workloads.
The author measured six realistic Spring Boot scenarios on PostgreSQL with over 40,000 records, comparing Spring Data JPA and native JDBC, and found JDBC to be 4‑460× faster for batch inserts, updates, deletes and complex statistics, while JPA remains adequate for small‑scale CRUD operations.
This guide explains how Apache AGE extends PostgreSQL with OpenCypher‑compatible graph capabilities, covering architecture, installation, storage schema, Cypher‑SQL integration, common graph operations, and a LangChain example that turns natural‑language questions into executable graph queries.
The article argues that a single PostgreSQL instance can handle caching, queuing, full‑text search, and real‑time notifications, eliminating the need for separate services like Redis, RabbitMQ, and Elasticsearch, while reducing cost and complexity.
This article compiles a detailed comparison of PostgreSQL and MySQL, highlighting PostgreSQL's lack of text‑size limits, better NULL handling, native array and JSON support, built‑in optimistic locking, superior GIS types, MVCC, flexible indexing, robust replication, and overall stability, while also noting the few areas where MySQL still holds an edge.
This article compares the execution‑plan generation, caching, and query‑performance characteristics of Oracle, MySQL, and PostgreSQL, explains how to view plans in each system, and provides practical tips for DBAs to interpret and optimize them effectively.
This guide walks through switching a SpringBoot + MyBatisPlus project from MySQL to PostgreSQL, covering driver setup, JDBC changes, numerous SQL syntax differences, type conversion issues, transaction handling, and provides helper scripts for bulk schema adjustments.
This comprehensive guide explains PostgreSQL backup and recovery techniques—including logical and physical backups, point‑in‑time recovery, automation scripts, security measures, and production‑grade best practices—to ensure data availability, integrity, and compliance.
PostgreSQL offers four transaction isolation levels—READ UNCOMMITTED, READ COMMITTED, REPEATABLE READ, and SERIALIZABLE—each preventing specific concurrency anomalies like dirty reads, non‑repeatable reads, and phantom reads, and the article explains their behavior, configuration commands, practical usage, performance trade‑offs, and production best practices.
This article explains why modern enterprises should avoid single‑database solutions, compares PostgreSQL and MongoDB across core philosophy, technical capabilities, ecosystem extensions, and cost, and provides a decision framework, real‑world case studies, and a hybrid architecture blueprint for scalable, low‑risk systems.
