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: postgres-17-json-table-memory-guardrail-postgres-17-json-113

Postgres 17 JSON_TABLE Memory Spill-to-Disk and Work_Mem Guardrails

ANSI SQL JSON_TABLE queries in PostgreSQL 17 evaluating complex nested paths on large payloads can exhaust backend work_mem and trigger OOM killer termination. Production query engines must bound session-level work_mem, enforce batching on incoming document batches, and constrain NESTED PATH tree depth to safely permit temp file spillover without process abortion. This invariant guarantees predictability under high-concurrency, bursty ingestion workloads.

Prohibited Anti-Pattern: Unbounded Nested JSON_TABLE Ingestion Exhausting Backend Memory

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Postgres 17 JSON_TABLE Memory Spill-to-Disk and Work_Mem Guardrails - ANSI SQL JSON_TABLE queries in PostgreSQL 17 evaluating complex nested paths on large payloads can exhaust backend work_mem and trigger OOM killer termination. Production query engines must bound session-level work_mem, enforce batching on incoming document batches, and constrain NESTED PATH tree depth to safely permit temp file spillover without process abortion. This invariant guarantees predictability under high-concurrency, bursty ingestion workloads.
globs: src/repositories/**/*.ts, src/services/**/*.ts, src/database/**/*.ts, migrations/**/*.sql
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/postgres-17-json-table-memory-guardrail-postgres-17-json-113"
---

# Postgres 17 JSON_TABLE Memory Spill-to-Disk and Work_Mem Guardrails

> **Severity**: CRITICAL | **Category**: backend
> **Anti-Pattern Warning**: Unbounded Nested JSON_TABLE Ingestion Exhausting Backend Memory

## System Constraints
You are a Principal Database Architect enforcing strict PostgreSQL 17 JSON_TABLE query safety invariants. You must block unbounded JSON_TABLE queries on large document arrays, enforce localized transaction-level work_mem and temp_file_limit controls, restrict deeply nested PATH clauses, and require client-side stream chunking before passing documents to PostgreSQL backend shredding.

## Strict Guidelines
- Engineers MUST ALWAYS chunk multi-megabyte JSON payloads in application memory before passing them to JSON_TABLE queries to prevent linear work_mem expansion.
- Engineers MUST configure session or transaction-level work_mem (e.g., SET LOCAL work_mem = '64MB') and explicit temp_file_limit guards when invoking queries with NESTED PATH clauses.
- Engineers MUST NOT allow client-supplied raw JSON arrays with unbounded nesting depth to be evaluated directly by recursive JSON_TABLE expressions.
- Code SHOULD specify explicit error behaviors (EMPTY ON ERROR or ERROR ON ERROR) for all column projections within JSON_TABLE to avoid silent data loss during disk spill.
- Services MUST monitor pg_stat_database.temp_files and pg_stat_database.temp_bytes to alert when JSON_TABLE query shredding exceeds disk spill baselines.

## Bad vs Good Implementations
### Unbounded JSON_TABLE vs. Safe Chunked JSON_TABLE with Local Memory Guard

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Passing an unbounded multi-megabyte JSON document into a single JSON_TABLE with NESTED PATH causes explosive backend memory allocation in PostgreSQL 17. If work_mem is exceeded or set too high without a transaction ceiling, concurrent workers run out of memory, risking Linux OOM-killer termination of the entire PostgreSQL postmaster.
```typescript
import { Pool } from 'pg';

export async function ingestDocumentBatch(pool: Pool, rawJsonPayload: string): Promise<void> {
  // ANTI-PATTERN: Executing nested JSON_TABLE on arbitrary sized monolithic payloads
  // Inherits default work_mem, risking Linux OOM aborts under concurrent burst traffic.
  const query = `
    INSERT INTO audit_records (id, event_name, entity_id, change_type, payload)
    SELECT jt.id, jt.event_name, jt.entity_id, jt.change_type, jt.payload
    FROM JSON_TABLE(
      $1::jsonb, '$[*]'
      COLUMNS (
        id text PATH '$.id',
        event_name text PATH '$.event',
        NESTED PATH '$.changes[*]'
        COLUMNS (
          entity_id bigint PATH '$.entity_id',
          change_type text PATH '$.type',
          payload jsonb PATH '$.details'
        )
      )
    ) AS jt;
  `;

  await pool.query(query, [rawJsonPayload]);
}
```

#### Production Standard (Correct)
> **Standard**: The payload is chunked on the application layer to bound JSON tree parsing overhead. Within the transaction, work_mem and temp_file_limit are explicitly scoped via SET LOCAL, preventing process memory bloat and stopping run-away recursive path evaluations before exhausting server memory.
```typescript
import { PoolClient, Pool } from 'pg';

interface ChangeItem {
  entity_id: number;
  type: string;
  details: Record<string, unknown>;
}

interface IngestionDoc {
  id: string;
  event: string;
  changes: ChangeItem[];
}

const BATCH_SIZE = 500;

export async function ingestDocumentBatch(
  pool: Pool,
  rawDocuments: IngestionDoc[]
): Promise<void> {
  const client: PoolClient = await pool.connect();
  try {
    for (let i = 0; i < rawDocuments.length; i += BATCH_SIZE) {
      const chunk = rawDocuments.slice(i, i + BATCH_SIZE);
      await client.query('BEGIN');
      
      // Invariant: Guard memory ceiling and temp disk budget for nested shredding
      await client.query("SET LOCAL work_mem = '32MB'");
      await client.query("SET LOCAL temp_file_limit = '256MB'");
      await client.query("SET LOCAL statement_timeout = '15s'");

      const query = `
        INSERT INTO audit_records (id, event_name, entity_id, change_type, payload)
        SELECT jt.id, jt.event_name, jt.entity_id, jt.change_type, jt.payload
        FROM JSON_TABLE(
          $1::jsonb, '$[*]'
          COLUMNS (
            id text PATH '$.id' ERROR ON ERROR,
            event_name text PATH '$.event' ERROR ON ERROR,
            NESTED PATH '$.changes[*]'
            COLUMNS (
              entity_id bigint PATH '$.entity_id',
              change_type text PATH '$.type',
              payload jsonb PATH '$.details'
            )
          )
        ) AS jt;
      `;
      
      await client.query(query, [JSON.stringify(chunk)]);
      await client.query('COMMIT');
    }
  } catch (err) {
    await client.query('ROLLBACK');
    throw err;
  } finally {
    client.release();
  }
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

PostgreSQL MCP Inspector
Enables inspection of PostgreSQL query execution plans, memory allocation stats, and EXPLAIN ANALYZE metrics.
Recommended Agent Skills (askills.dev)

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

Postgres Plan Cost Analyzer
Analyzes Postgres execution plans to detect temp file spills and excessive internal node memory consumption.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Postgres 17 JSON_TABLE Memory Spill-to-Disk and Work_Mem Guardrails

Postgres 17 JSON_TABLE Memory Spill-to-Disk and Work_Mem Guardrails defines an industrial-grade behavioral standard for backend engineering. ANSI SQL JSON_TABLE queries in PostgreSQL 17 evaluating complex nested paths on large payloads can exhaust backend work_mem and trigger OOM killer termination. Production query engines must bound session-level work_mem, enforce batching on incoming document batches, and constrain NESTED PATH tree depth to safely permit temp file spillover without process abortion. This invariant guarantees predictability under high-concurrency, bursty ingestion workloads. 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 Nested JSON_TABLE Ingestion Exhausting Backend Memory 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 Nested JSON_TABLE Ingestion Exhausting Backend MemoryCritical
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 chunk multi-megabyte JSON payloads in application memory before passing them to JSON_TABLE queries to prevent linear work_mem expansion.

Engineers MUST ALWAYS chunk multi-megabyte JSON payloads in application memory before passing them to JSON_TABLE queries to prevent linear work_mem expansion.

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 configure session or transaction-level work_mem (e.g., SET LOCAL work_mem = '64MB') and explicit temp_file_limit guards when invoking queries with NESTED PATH clauses.

Engineers MUST configure session or transaction-level work_mem (e.g., SET LOCAL work_mem = '64MB') and explicit temp_file_limit guards when invoking queries with NESTED PATH clauses.

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

Engineers MUST NOT allow client-supplied raw JSON arrays with unbounded nesting depth to be evaluated directly by recursive JSON_TABLE expressions.

Engineers MUST NOT allow client-supplied raw JSON arrays with unbounded nesting depth to be evaluated directly by recursive JSON_TABLE expressions.

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

Code SHOULD specify explicit error behaviors (EMPTY ON ERROR or ERROR ON ERROR) for all column projections within JSON_TABLE to avoid silent data loss during disk spill.

Code SHOULD specify explicit error behaviors (EMPTY ON ERROR or ERROR ON ERROR) for all column projections within JSON_TABLE to avoid silent data loss during disk spill.

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

Services MUST monitor pg_stat_database.temp_files and pg_stat_database.temp_bytes to alert when JSON_TABLE query shredding exceeds disk spill baselines.

Services MUST monitor pg_stat_database.temp_files and pg_stat_database.temp_bytes to alert when JSON_TABLE query shredding exceeds disk spill baselines.

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 Postgres 17 JSON_TABLE Memory Spill-to-Disk and Work_Mem Guardrails critical for AI coding assistants?

ANSI SQL JSON_TABLE queries in PostgreSQL 17 evaluating complex nested paths on large payloads can exhaust backend work_mem and trigger OOM killer termination. Production query engines must bound session-level work_mem, enforce batching on incoming document batches, and constrain NESTED PATH tree depth to safely permit temp file spillover without process abortion. This invariant guarantees predictability under high-concurrency, bursty ingestion workloads. 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 Nested JSON_TABLE Ingestion Exhausting Backend Memory) 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

Postgres