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-json-table-workmem-spill-containment

PostgreSQL 17 JSON_TABLE WorkMem Allocation & Spill Containment Standard

Governs execution bounds and streaming memory limits for PostgreSQL 17 SQL/JSON JSON_TABLE transformations over nested hierarchical documents. Mandates explicit work_mem thresholds, temp_file_limit spill containment, and keyset-chunked projection to prevent Linux OOM-killer invocations and cluster-wide postmaster panics.

Prohibited Anti-Pattern: Unbounded Single-Query JSON_TABLE Materialization Triggering Fatal Backend Process OOM

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: PostgreSQL 17 JSON_TABLE WorkMem Allocation & Spill Containment Standard - Governs execution bounds and streaming memory limits for PostgreSQL 17 SQL/JSON JSON_TABLE transformations over nested hierarchical documents. Mandates explicit work_mem thresholds, temp_file_limit spill containment, and keyset-chunked projection to prevent Linux OOM-killer invocations and cluster-wide postmaster panics.
globs: src/**/*.sql, src/**/*.ts, src/repositories/**/*.ts, src/database/**/*.ts, migrations/**/*.sql
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/pg17-json-table-workmem-spill-containment"
---

# PostgreSQL 17 JSON_TABLE WorkMem Allocation & Spill Containment Standard

> **Severity**: CRITICAL | **Category**: backend
> **Anti-Pattern Warning**: Unbounded Single-Query JSON_TABLE Materialization Triggering Fatal Backend Process OOM

## System Constraints
You are a Principal Database Architect enforcing strict PostgreSQL 17 JSON_TABLE memory safety invariants. Mandate that every execution of JSON_TABLE operating over unbounded, nested, or batched JSON/JSONB documents enforces transactional containment using SET LOCAL work_mem, SET LOCAL temp_file_limit, and chunked cursor evaluation to prevent runaway backend memory allocation and postmaster SIGKILL crashes.

## Strict Guidelines
- Engineers MUST ALWAYS isolate JSON_TABLE queries processing large or variable-depth payloads within dedicated transactions configured with constrained 'SET LOCAL work_mem' and 'SET LOCAL temp_file_limit'.
- Engineers MUST NOT execute recursive or multi-tier NESTED PATH expressions in JSON_TABLE across batch document sets without keyset or cursor chunking.
- Code SHOULD enforce strict SQL/JSON error handling clauses (ON ERROR EMPTY / ON EMPTY EMPTY) instead of allowing unbounded error-context allocations during malformed document parsing.
- Services MUST stream high-volume JSON transformations in deterministic row slices (e.g., maximum batch size of 500-1000 records per transaction) rather than passing monolithic JSON arrays to JSON_TABLE.
- Database components NEVER execute raw JSON_TABLE joins against unindexed or unpartitioned tables without explicit planner cost bounds and statement timeouts.

## Bad vs Good Implementations
### Memory-Safe Keyset-Chunked JSON_TABLE Transformation

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Executes multi-level NESTED PATH JSON_TABLE over every row in raw_audit_documents simultaneously without memory bounds. When JSON documents are large or deeply nested, Postgres backend process memory explodes beyond OS limits, triggering a SIGKILL and terminating all concurrent connections via postmaster recovery.
```typescript
import { Pool } from 'pg';

export async function flattenNestedAuditLogs(pool: Pool): Promise<void> {
  // ANTI-PATTERN: Unbounded JSON_TABLE over all rows in a single statement without
  // work_mem restrictions, temp file limits, or batching. Multi-level nested path evaluation
  // consumes gigabytes of backend memory on deep documents, triggering Linux OOM killer.
  await pool.query(`
    INSERT INTO audit_log_events (document_id, event_type, event_payload, actor_id)
    SELECT 
      doc.id,
      jt.event_type,
      jt.payload,
      jt.actor_id
    FROM raw_audit_documents doc,
    JSON_TABLE(
      doc.payload_jsonb,
      '$.events[*]'
      COLUMNS (
        event_type text PATH '$.type',
        NESTED PATH '$.sub_events[*]'
        COLUMNS (
          payload text PATH '$.data',
          actor_id uuid PATH '$.metadata.actor'
        )
      )
    ) AS jt;
  `);
}
```

#### Production Standard (Correct)
> **Standard**: Wraps JSON_TABLE in deterministic keyset batches with transactional work_mem and temp_file_limit bounds. This limits per-operation memory footprint to 32MB and disk spill to 512MB, preventing OOM terminations while maintaining predictable latency and rollback boundaries.
```typescript
import { Pool, PoolClient } from 'pg';

const BATCH_SIZE = 500;

export async function flattenNestedAuditLogs(pool: Pool): Promise<void> {
  let lastProcessedId = '00000000-0000-0000-0000-000000000000';
  let hasMore = true;

  while (hasMore) {
    const client: PoolClient = await pool.connect();
    try {
      await client.query('BEGIN TRANSACTION ISOLATION LEVEL READ COMMITTED');
      // PRODUCTION INVARIANT: Contain backend memory allocation and spill to disk safely
      await client.query("SET LOCAL work_mem = '32MB'");
      await client.query("SET LOCAL temp_file_limit = '512MB'");
      await client.query("SET LOCAL statement_timeout = '15000'");

      const result = await client.query({
        text: `
          WITH batch AS (
            SELECT id, payload_jsonb
            FROM raw_audit_documents
            WHERE id > $1
            ORDER BY id ASC
            LIMIT $2
          )
          INSERT INTO audit_log_events (document_id, event_type, event_payload, actor_id)
          SELECT 
            batch.id,
            jt.event_type,
            jt.payload,
            jt.actor_id
          FROM batch,
          JSON_TABLE(
            batch.payload_jsonb,
            '$.events[*]'
            ERROR ON ERROR
            COLUMNS (
              event_type text PATH '$.type',
              NESTED PATH '$.sub_events[*]'
              COLUMNS (
                payload text PATH '$.data',
                actor_id uuid PATH '$.metadata.actor'
              )
            )
          ) AS jt
          RETURNING batch.id;
        `,
        values: [lastProcessedId, BATCH_SIZE],
      });

      if (result.rowCount === 0) {
        hasMore = false;
      } else {
        lastProcessedId = result.rows[result.rows.length - 1].id;
      }

      await client.query('COMMIT');
    } catch (error) {
      await client.query('ROLLBACK');
      throw error;
    } finally {
      client.release();
    }
  }
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

PostgreSQL Context Server
Inspects live PostgreSQL execution plans (EXPLAIN ANALYZE) and monitors temporary file usage and memory allocation across queries.
Recommended Agent Skills (askills.dev)

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

PostgreSQL Explain Analyzer Skill
CLI skill that parses query plans for JSON_TABLE node memory spikes, temp file spills, and sequential scan hazards.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: PostgreSQL 17 JSON_TABLE WorkMem Allocation & Spill Containment Standard

PostgreSQL 17 JSON_TABLE WorkMem Allocation & Spill Containment Standard defines an industrial-grade behavioral standard for backend engineering. Governs execution bounds and streaming memory limits for PostgreSQL 17 SQL/JSON JSON_TABLE transformations over nested hierarchical documents. Mandates explicit work_mem thresholds, temp_file_limit spill containment, and keyset-chunked projection to prevent Linux OOM-killer invocations and cluster-wide postmaster panics. 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: Unbounded Single-Query JSON_TABLE Materialization Triggering Fatal Backend Process OOM 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 DriftUnbounded Single-Query JSON_TABLE Materialization Triggering Fatal Backend Process OOMCritical
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 isolate JSON_TABLE queries processing large or variable-depth payloads within dedicated transactions configured with constrained 'SET LOCAL work_mem' and 'SET LOCAL temp_file_limit'.

Engineers MUST ALWAYS isolate JSON_TABLE queries processing large or variable-depth payloads within dedicated transactions configured with constrained 'SET LOCAL work_mem' and 'SET LOCAL temp_file_limit'.

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 execute recursive or multi-tier NESTED PATH expressions in JSON_TABLE across batch document sets without keyset or cursor chunking.

Engineers MUST NOT execute recursive or multi-tier NESTED PATH expressions in JSON_TABLE across batch document sets without keyset or cursor chunking.

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

Code SHOULD enforce strict SQL/JSON error handling clauses (ON ERROR EMPTY / ON EMPTY EMPTY) instead of allowing unbounded error-context allocations during malformed document parsing.

Code SHOULD enforce strict SQL/JSON error handling clauses (ON ERROR EMPTY / ON EMPTY EMPTY) instead of allowing unbounded error-context allocations during malformed document parsing.

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

Services MUST stream high-volume JSON transformations in deterministic row slices (e.g., maximum batch size of 500-1000 records per transaction) rather than passing monolithic JSON arrays to JSON_TABLE.

Services MUST stream high-volume JSON transformations in deterministic row slices (e.g., maximum batch size of 500-1000 records per transaction) rather than passing monolithic JSON arrays to JSON_TABLE.

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

Database components NEVER execute raw JSON_TABLE joins against unindexed or unpartitioned tables without explicit planner cost bounds and statement timeouts.

Database components NEVER execute raw JSON_TABLE joins against unindexed or unpartitioned tables without explicit planner cost bounds and statement timeouts.

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 JSON_TABLE WorkMem Allocation & Spill Containment Standard critical for AI coding assistants?

Governs execution bounds and streaming memory limits for PostgreSQL 17 SQL/JSON JSON_TABLE transformations over nested hierarchical documents. Mandates explicit work_mem thresholds, temp_file_limit spill containment, and keyset-chunked projection to prevent Linux OOM-killer invocations and cluster-wide postmaster panics. 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 (Unbounded Single-Query JSON_TABLE Materialization Triggering Fatal Backend Process OOM) 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