惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

量子位
Stack Overflow Blog
Stack Overflow Blog
人人都是产品经理
人人都是产品经理
The GitHub Blog
The GitHub Blog
Engineering at Meta
Engineering at Meta
Vercel News
Vercel News
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Y
Y Combinator Blog
The Cloudflare Blog
Last Week in AI
Last Week in AI
B
Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
T
Tailwind CSS Blog
V
Visual Studio Blog
博客园 - 三生石上(FineUI控件)
小众软件
小众软件
Google DeepMind News
Google DeepMind News
D
DataBreaches.Net
博客园 - 司徒正美
B
Blog RSS Feed
Microsoft Azure Blog
Microsoft Azure Blog
罗磊的独立博客
Hugging Face - Blog
Hugging Face - Blog
L
LangChain Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Scaling to a Billion Rows: PostgreSQL Partitioning in Lar...
Prajapati Paresh · 2026-06-16 · via DEV Community

The 100-Million Row Wall

In enterprise B2B SaaS platforms at Smart Tech Devs, tracking historical data is a compliance requirement. Tables like audit_logs, api_requests, or telemetry_events grow exponentially. When a single PostgreSQL table hits 100 million rows, standard B-Tree indexes become massive and no longer fit into RAM. Query performance degrades from milliseconds to seconds.

Worse, pruning old data becomes an operational nightmare. Running a standard DELETE FROM audit_logs WHERE created_at < '2022-01-01' on a massive table will trigger a massive transaction lock, block incoming inserts, and bloat the database with dead tuples (requiring expensive VACUUM operations). To architect for infinite scale, you must break the monolith using Table Partitioning.

The Solution: Range Partitioning

PostgreSQL Native Table Partitioning allows you to split one massive logical table into multiple smaller physical tables under the hood. For time-series data, we use Range Partitioning by month.

To the Laravel application, you still query AuditLog::all(). But PostgreSQL intercepts the query and instantly routes it to the specific physical table (e.g., audit_logs_2026_06). When you need to delete data older than 2 years, you simply drop the old partition table. It happens in 10 milliseconds, uses zero CPU, and creates zero table locks.

Step 1: Architecting the Partitioned Migration

Laravel's default Blueprint doesn't support native partitioning, so we drop down to raw SQL in our migration to establish the root table and the first few monthly partitions.


use Illuminate\Database\Migrations\Migration;
use Illuminate\Support\Facades\DB;

class CreatePartitionedAuditLogsTable extends Migration
{
    public function up(): void
    {
        // 1. Create the Master Table (Logical wrapper)
        // Notice we do NOT create a standard primary key, as partition keys 
        // must be part of any unique index.
        DB::statement('
            CREATE TABLE audit_logs (
                id UUID NOT NULL,
                tenant_id BIGINT NOT NULL,
                action VARCHAR(255) NOT NULL,
                created_at TIMESTAMP(0) WITHOUT TIME ZONE NOT NULL
            ) PARTITION BY RANGE (created_at);
        ');

        // 2. Create the Physical Partitions for upcoming months
        DB::statement("
            CREATE TABLE audit_logs_2026_05 
            PARTITION OF audit_logs 
            FOR VALUES FROM ('2026-05-01 00:00:00') TO ('2026-06-01 00:00:00');
        ");

        DB::statement("
            CREATE TABLE audit_logs_2026_06 
            PARTITION OF audit_logs 
            FOR VALUES FROM ('2026-06-01 00:00:00') TO ('2026-07-01 00:00:00');
        ");

        // 3. Create indexes ON the master table (PostgreSQL auto-applies them to partitions)
        DB::statement('CREATE INDEX audit_logs_tenant_idx ON audit_logs (tenant_id);');
    }

    public function down(): void
    {
        DB::statement('DROP TABLE IF EXISTS audit_logs CASCADE;');
    }
}

Step 2: Automating Future Partitions

Because you cannot insert data into a partition that doesn't exist, you must automate partition creation. In Laravel, we set up a simple scheduled Command that runs on the 25th of every month to create the physical table for the next month.


// app/Console/Commands/CreateNextMonthPartition.php
$nextMonth = now()->addMonth();
$tableName = 'audit_logs_' . $nextMonth->format('Y_m');

$start = $nextMonth->startOfMonth()->toDateTimeString();
$end = $nextMonth->addMonth()->startOfMonth()->toDateTimeString();

DB::statement("
    CREATE TABLE IF NOT EXISTS {$tableName} 
    PARTITION OF audit_logs 
    FOR VALUES FROM ('{$start}') TO ('{$end}');
");

The Engineering ROI

Table Partitioning is the ultimate database scalability pattern for time-series logs. It keeps your active indexes small and fully loaded in RAM, making recent data queries blazingly fast. More importantly, it turns the terrifying operation of deleting 50 million old records into a harmless, 10-millisecond DROP TABLE command, ensuring your SaaS never experiences a maintenance window crash.