AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
backendcritical PriorityID: pg17-incremental-backup-block-tracking-invariants

PostgreSQL 17 Incremental Backup & WAL Summarization Invariants

Enforces continuous write-ahead log (WAL) summarization and deterministic block-level delta tracking in PostgreSQL 17 to prevent full-table relation scans during multi-terabyte backups. Eliminates I/O freeze windows and checkpoint spikes by asserting backup manifest chain continuity and validating WAL summary ranges prior to pg_combinebackup execution. Protects high-throughput transactional engines from catastrophic recovery latency and disk bandwidth saturation.

Prohibited Anti-Pattern: Executing Unverified Basebackups or Severing WAL Summarization Chains Leading to Catastrophic Full I/O Re-Scans

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: PostgreSQL 17 Incremental Backup & WAL Summarization Invariants - Enforces continuous write-ahead log (WAL) summarization and deterministic block-level delta tracking in PostgreSQL 17 to prevent full-table relation scans during multi-terabyte backups. Eliminates I/O freeze windows and checkpoint spikes by asserting backup manifest chain continuity and validating WAL summary ranges prior to pg_combinebackup execution. Protects high-throughput transactional engines from catastrophic recovery latency and disk bandwidth saturation.
globs: src/**/*.ts, src/db/**/*.ts, src/backup/**/*.ts, src/infrastructure/**/*.ts, infra/**/*.ts
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/pg17-incremental-backup-block-tracking-invariants"
---

# PostgreSQL 17 Incremental Backup & WAL Summarization Invariants

> **Severity**: CRITICAL | **Category**: backend
> **Anti-Pattern Warning**: Executing Unverified Basebackups or Severing WAL Summarization Chains Leading to Catastrophic Full I/O Re-Scans

## System Constraints
You are a Principal Software Architect enforcing PostgreSQL 17 Incremental Backup Block Tracking Invariants. Mandate that all incremental backup orchestration services guarantee continuous WAL summarization (summarize_wal = on), strictly validate LSN intervals against backup_manifest files, verify WAL summary continuity via pg_wal_summary_dump or syscatalog inspection before delta extraction, and guarantee non-blocking recovery assembly via pg_combinebackup.

## Strict Guidelines
- Engineers MUST ALWAYS verify that PostgreSQL 17 'summarize_wal' is enabled and that WAL summary files in 'pg_wal/summaries' cover the full [start_lsn, end_lsn) range prior to initiating an incremental delta run.
- Engineers MUST NOT trigger an incremental backup using 'pg_basebackup --incremental' against a parent manifest whose terminal LSN does not align contiguously with available WAL summary segments.
- Services MUST execute deterministic manifest checksum and LSN continuity verification before feeding manifest chains to 'pg_combinebackup'.
- Components NEVER fall back to unthrottled full relation scans during backup windows without explicit operator-driven circuit breaking and telemetry alerts.
- Code SHOULD enforce strict LSN monotonic increment checks between parent and child manifests to prevent divergent timeline delta corruption.

## Bad vs Good Implementations
### PostgreSQL 17 Incremental Manifest and WAL Summary Continuity Validation

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The bad example executes pg_basebackup with an unverified manifest path without asserting WAL summarizer status ('summarize_wal = on') or validating that WAL summaries are continuous between parent and child. If WAL summaries are purged or missing, PostgreSQL fails over or saturates disk I/O, causing severe query latency and potential restore failure.
```typescript
import { exec } from 'node:child_process';
import { promisify } from 'node:util';

const execAsync = promisify(exec);

interface BackupOptions {
  parentManifestPath: string;
  targetDir: string;
  dbHost: string;
}

// ANTI-PATTERN: Naively calling pg_basebackup with incremental flag
// without validating WAL summarization state or LSN boundary continuity.
export async function triggerIncrementalBackup(options: BackupOptions): Promise<void> {
  const command = `pg_basebackup -h ${options.dbHost} -D ${options.targetDir} --incremental=${options.parentManifestPath} --format=tar`;
  
  // Unchecked execution causes severe I/O stall if WAL summaries are missing
  // or triggers silent corruption if manifests belong to divergent timelines.
  await execAsync(command);
}
```

#### Production Standard (Correct)
> **Standard**: The corrected implementation enforces PostgreSQL 17 invariants: it asserts that summarize_wal is enabled, parses the parent manifest's terminal LSN, queries pg_available_wal_summaries() to guarantee summary coverage across the exact boundary, and explicitly selects SHA256 manifest checksums while invoking pg_basebackup via a non-shell execFile process.
```typescript
import { execFile } from 'node:child_process';
import { promisify } from 'node:util';
import { readFile } from 'node:fs/promises';
import { Client } from 'pg';

const execFileAsync = promisify(execFile);

interface BackupManifest {
  "PostgreSQL-Backup-Manifest-Version": number;
  Files: Record<string, { Size: number; Checksum: string }>;
  "WAL-Ranges": Array<{ Timeline: number; Start_LSN: string; End_LSN: string }>;
  "End-LSN": string;
}

interface BackupOptions {
  parentManifestPath: string;
  targetDir: string;
  dbClient: Client;
  dbHost: string;
  dbPort: number;
}

export async function executeDeterministicIncrementalBackup(options: BackupOptions): Promise<void> {
  // 1. Verify WAL summarization invariant in PostgreSQL 17
  const gucRes = await options.dbClient.query(
    "SELECT current_setting('summarize_wal') AS summarize_wal, current_setting('server_version_num')::int AS version"
  );
  const { summarize_wal, version } = gucRes.rows[0];
  if (version < 170000 || summarize_wal !== 'on') {
    throw new Error(`PostgreSQL 17+ with summarize_wal=on required. Found version=${version}, summarize_wal=${summarize_wal}`);
  }

  // 2. Parse parent manifest to identify required lower-bound LSN
  const rawManifest = await readFile(options.parentManifestPath, 'utf8');
  const manifest: BackupManifest = JSON.parse(rawManifest);
  const parentEndLsn = manifest['End-LSN'];

  // 3. Ensure WAL summary records continuously cover parentEndLsn to current WAL insertion
  const summaryCheck = await options.dbClient.query(
    `SELECT count(*)::int AS missing_ranges
     FROM pg_available_wal_summaries()
     WHERE tli = (SELECT timeline_id FROM pg_control_checkpoint())
       AND end_lsn >= $1::pg_lsn
       AND start_lsn <= $1::pg_lsn;`,
    [parentEndLsn]
  );

  if (summaryCheck.rows[0].missing_ranges === 0) {
    throw new Error(`WAL summary gap detected for LSN ${parentEndLsn}. Cannot guarantee delta consistency without I/O stall.`);
  }

  // 4. Execute atomic incremental basebackup using strictly vetted manifest
  await execFileAsync('pg_basebackup', [
    `-h`, options.dbHost,
    `-p`, options.dbPort.toString(),
    `-D`, options.targetDir,
    `--incremental=${options.parentManifestPath}`,
    `--format=tar`,
    `--manifest-checksums=SHA256`,
    `--no-sync`
  ]);
}
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

PostgreSQL Dynamic Inspector MCP
Inspects PostgreSQL GUCs, WAL summarizer worker status, and checkpoint statistics in real time.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

PostgreSQL 17 Synthetic Restore Validator
CLI automation skill to test synthetic full backup generation and manifest consistency using pg_combinebackup in isolated sandboxes.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: PostgreSQL 17 Incremental Backup & WAL Summarization Invariants

PostgreSQL 17 Incremental Backup & WAL Summarization Invariants defines an industrial-grade behavioral standard for backend engineering. Enforces continuous write-ahead log (WAL) summarization and deterministic block-level delta tracking in PostgreSQL 17 to prevent full-table relation scans during multi-terabyte backups. Eliminates I/O freeze windows and checkpoint spikes by asserting backup manifest chain continuity and validating WAL summary ranges prior to pg_combinebackup execution. Protects high-throughput transactional engines from catastrophic recovery latency and disk bandwidth saturation. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Executing Unverified Basebackups or Severing WAL Summarization Chains Leading to Catastrophic Full I/O Re-Scans Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftExecuting Unverified Basebackups or Severing WAL Summarization Chains Leading to Catastrophic Full I/O Re-ScansCritical
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Engineers MUST ALWAYS verify that PostgreSQL 17 'summarize_wal' is enabled and that WAL summary files in 'pg_wal/summaries' cover the full [start_lsn, end_lsn) range prior to initiating an incremental delta run.

Engineers MUST ALWAYS verify that PostgreSQL 17 'summarize_wal' is enabled and that WAL summary files in 'pg_wal/summaries' cover the full [start_lsn, end_lsn) range prior to initiating an incremental delta run.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST NOT trigger an incremental backup using 'pg_basebackup --incremental' against a parent manifest whose terminal LSN does not align contiguously with available WAL summary segments.

Engineers MUST NOT trigger an incremental backup using 'pg_basebackup --incremental' against a parent manifest whose terminal LSN does not align contiguously with available WAL summary segments.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Services MUST execute deterministic manifest checksum and LSN continuity verification before feeding manifest chains to 'pg_combinebackup'.

Services MUST execute deterministic manifest checksum and LSN continuity verification before feeding manifest chains to 'pg_combinebackup'.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Components NEVER fall back to unthrottled full relation scans during backup windows without explicit operator-driven circuit breaking and telemetry alerts.

Components NEVER fall back to unthrottled full relation scans during backup windows without explicit operator-driven circuit breaking and telemetry alerts.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Code SHOULD enforce strict LSN monotonic increment checks between parent and child manifests to prevent divergent timeline delta corruption.

Code SHOULD enforce strict LSN monotonic increment checks between parent and child manifests to prevent divergent timeline delta corruption.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is PostgreSQL 17 Incremental Backup & WAL Summarization Invariants critical for AI coding assistants?

Enforces continuous write-ahead log (WAL) summarization and deterministic block-level delta tracking in PostgreSQL 17 to prevent full-table relation scans during multi-terabyte backups. Eliminates I/O freeze windows and checkpoint spikes by asserting backup manifest chain continuity and validating WAL summary ranges prior to pg_combinebackup execution. Protects high-throughput transactional engines from catastrophic recovery latency and disk bandwidth saturation. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Executing Unverified Basebackups or Severing WAL Summarization Chains Leading to Catastrophic Full I/O Re-Scans) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related BACKEND Rules

View all rules →
backend
42

Fastify 5 Schema Compilers & Encapsulation Production Standard

Fastify relies on lexical encapsulation contexts to sandbox decorators, hooks, and compiled validation/serialization schemas without memory leaks or cross-tenant bleed. In Fastify 5, misuse of global compilers or failing to encapsulate plugin boundaries causes compiled `fast-json-stringify` serializers and Ajv validators to either crash on duplicate IDs, leak private data across sibling scopes, or bypass JIT compilation optimizations. Production services must enforce strict encapsulation hierarchies and type-safe schema compilation across every routing subtree.

backend
68

Bun Embedded SQLite WAL Mode & Transaction Synchronization Standard

Production database standard for bun:sqlite. Mandates enabling Write-Ahead Logging (PRAGMA journal_mode = WAL), busy timeouts, and using db.transaction() for atomic operations without lock starvation.

backend
68

Drizzle ORM Batch API & Interactive Transaction Isolation Standard

Production database standard for Drizzle ORM (PostgreSQL & MySQL). Mandates using db.batch() over HTTP drivers to prevent round-trip waterfalls, explicit db.transaction() with serializable/read-committed isolation, and strictly avoids unawaited query promises.

1 Rule in Stack

PostgreSQL