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-allocation-bound

Postgres 17 JSON_TABLE Memory Allocation Bound & Execution Ceiling

Enforces strict transaction-scoped memory allocation limits and row-projection caps on PostgreSQL 17 SQL/JSON JSON_TABLE queries. Deeply nested JSON path evaluations and unbounded NESTED PATH clauses expand combinatorially in backend process memory, requiring explicit SET LOCAL work_mem boundaries and deterministic pagination to prevent backend Out-Of-Memory (OOM) process termination and connection drops.

Prohibited Anti-Pattern: Unbounded JSON_TABLE Queries with Deeply Nested Paths Over Exhaustible Connection Pools

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Postgres 17 JSON_TABLE Memory Allocation Bound & Execution Ceiling - Enforces strict transaction-scoped memory allocation limits and row-projection caps on PostgreSQL 17 SQL/JSON JSON_TABLE queries. Deeply nested JSON path evaluations and unbounded NESTED PATH clauses expand combinatorially in backend process memory, requiring explicit SET LOCAL work_mem boundaries and deterministic pagination to prevent backend Out-Of-Memory (OOM) process termination and connection drops.
globs: src/repositories/**/*.ts, src/services/**/*.ts, src/db/**/*.ts, src/analytics/**/*.ts
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/postgres-17-json-table-memory-allocation-bound"
---

# Postgres 17 JSON_TABLE Memory Allocation Bound & Execution Ceiling

> **Severity**: CRITICAL | **Category**: backend
> **Anti-Pattern Warning**: Unbounded JSON_TABLE Queries with Deeply Nested Paths Over Exhaustible Connection Pools

## System Constraints
You are a Principal Database Reliability Engineer enforcing strict operational boundaries on PostgreSQL 17 JSON_TABLE operations. Mandate transaction-scoped `SET LOCAL work_mem` and `SET LOCAL statement_timeout` invocations prior to executing SQL/JSON transformations with complex or nested path expressions. Ensure all queries define strict error-handling semantics (`ON ERROR`), explicit column types without implicit text coercion, and chunked cursor-based pagination to prevent backend memory exhaustion and OS killer invocations.

## Strict Guidelines
- Engineers MUST ALWAYS isolate SQL/JSON `JSON_TABLE` operations within an explicit transaction setting `SET LOCAL work_mem` to a safe operational ceiling (e.g., <= 64MB) and bounded `statement_timeout`.
- Engineers MUST NOT execute `JSON_TABLE` queries with multiple `NESTED PATH` clauses against multi-gigabyte or unpaginated JSONB tables in default auto-commit connection states.
- Code SHOULD specify explicit `ERROR ON ERROR` or `EMPTY ON ERROR` clauses in `JSON_TABLE` column projections to avoid silent memory leaks or unhandled transaction rollbacks during path parsing.
- Services MUST enforce upper bounds (`LIMIT` clause or deterministic chunking) on the source record set feeding into `JSON_TABLE` lateral joins.
- Components NEVER execute raw or dynamic JSONPath strings passed directly from user input without schema-level structural validation.

## Bad vs Good Implementations
### Unbounded JSON_TABLE Lateral Join vs. Scoped Memory Safe Extraction

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Executing JSON_TABLE with NESTED PATH in default autocommit mode without transaction-scoped work_mem bounds or LIMIT clauses risks explosive Cartesian row generation in PostgreSQL backend process memory, often triggering an OS OOM killer event.
```typescript
import { Pool } from 'pg';

export async function extractAnalyticsEvents(pool: Pool, datasetId: string) {
  // BAD: Executes unbounded JSON_TABLE query in autocommit mode.
  // Deeply nested JSON array expansion inherits global work_mem and has no statement timeout.
  // High cardinality payload will balloon backend process RSS and trigger Postgres OOM kills.
  const query = `
    SELECT 
      jt.event_id,
      jt.event_name,
      jt.metric_value
    FROM analytics_payloads ap,
    JSON_TABLE(
      ap.raw_payload,
      '$.metrics[*]' COLUMNS (
        event_id text PATH '$.id',
        event_name text PATH '$.name',
        NESTED PATH '$.dimensions[*]'
        COLUMNS (
          metric_value numeric PATH '$.value'
        )
      )
    ) AS jt
    WHERE ap.dataset_id = $1;
  `;
  const result = await pool.query(query, [datasetId]);
  return result.rows;
}
```

#### Production Standard (Correct)
> **Standard**: Wraps the JSON_TABLE extraction in a READ ONLY transaction, sets explicit LOCAL ceilings for work_mem and statement_timeout, pre-filters and limits the source payload cardinality, and provides resilient EMPTY ON ERROR handling for dynamic JSON properties.
```typescript
import { Pool, PoolClient } from 'pg';

interface AnalyticsEvent {
  eventId: string;
  eventName: string;
  metricValue: number;
}

export async function extractAnalyticsEventsSafe(
  pool: Pool,
  datasetId: string,
  batchLimit = 1000
): Promise<AnalyticsEvent[]> {
  const client: PoolClient = await pool.connect();
  try {
    await client.query('BEGIN READ ONLY');
    // Guard backend memory and query execution window
    await client.query("SET LOCAL work_mem = '32MB'");
    await client.query("SET LOCAL statement_timeout = '15000ms'");

    const query = `
      SELECT 
        jt.event_id AS "eventId",
        jt.event_name AS "eventName",
        jt.metric_value AS "metricValue"
      FROM (
        SELECT raw_payload
        FROM analytics_payloads
        WHERE dataset_id = $1
        ORDER BY created_at DESC
        LIMIT $2
      ) ap,
      JSON_TABLE(
        ap.raw_payload,
        '$.metrics[*]' PASSING ap.raw_payload
        COLUMNS (
          event_id text PATH '$.id' ERROR ON ERROR,
          event_name text PATH '$.name' EMPTY ON ERROR,
          NESTED PATH '$.dimensions[*]'
          COLUMNS (
            metric_value numeric PATH '$.value' EMPTY ON ERROR
          )
        )
      ) AS jt;
    `;
    
    const { rows } = await client.query<AnalyticsEvent>(query, [datasetId, batchLimit]);
    await client.query('COMMIT');
    return rows;
  } 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 MCP Server
Inspects query execution plans, memory usage stats, and EXPLAIN ANALYZE traces directly from Claude or Cursor.
Recommended Agent Skills (askills.dev)

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

PostgreSQL Query Performance Explainer
Analyzes complex SQL/JSON execution plans to flag buffer allocations and potential memory exhaustion before production migration.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Postgres 17 JSON_TABLE Memory Allocation Bound & Execution Ceiling

Postgres 17 JSON_TABLE Memory Allocation Bound & Execution Ceiling defines an industrial-grade behavioral standard for backend engineering. Enforces strict transaction-scoped memory allocation limits and row-projection caps on PostgreSQL 17 SQL/JSON JSON_TABLE queries. Deeply nested JSON path evaluations and unbounded NESTED PATH clauses expand combinatorially in backend process memory, requiring explicit SET LOCAL work_mem boundaries and deterministic pagination to prevent backend Out-Of-Memory (OOM) process termination and connection drops. 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 JSON_TABLE Queries with Deeply Nested Paths Over Exhaustible Connection Pools 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 JSON_TABLE Queries with Deeply Nested Paths Over Exhaustible Connection PoolsCritical
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 SQL/JSON `JSON_TABLE` operations within an explicit transaction setting `SET LOCAL work_mem` to a safe operational ceiling (e.g., <= 64MB) and bounded `statement_timeout`.

Engineers MUST ALWAYS isolate SQL/JSON `JSON_TABLE` operations within an explicit transaction setting `SET LOCAL work_mem` to a safe operational ceiling (e.g., <= 64MB) and bounded `statement_timeout`.

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 `JSON_TABLE` queries with multiple `NESTED PATH` clauses against multi-gigabyte or unpaginated JSONB tables in default auto-commit connection states.

Engineers MUST NOT execute `JSON_TABLE` queries with multiple `NESTED PATH` clauses against multi-gigabyte or unpaginated JSONB tables in default auto-commit connection states.

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 specify explicit `ERROR ON ERROR` or `EMPTY ON ERROR` clauses in `JSON_TABLE` column projections to avoid silent memory leaks or unhandled transaction rollbacks during path parsing.

Code SHOULD specify explicit `ERROR ON ERROR` or `EMPTY ON ERROR` clauses in `JSON_TABLE` column projections to avoid silent memory leaks or unhandled transaction rollbacks during path 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 enforce upper bounds (`LIMIT` clause or deterministic chunking) on the source record set feeding into `JSON_TABLE` lateral joins.

Services MUST enforce upper bounds (`LIMIT` clause or deterministic chunking) on the source record set feeding into `JSON_TABLE` lateral joins.

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

Components NEVER execute raw or dynamic JSONPath strings passed directly from user input without schema-level structural validation.

Components NEVER execute raw or dynamic JSONPath strings passed directly from user input without schema-level structural validation.

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 Allocation Bound & Execution Ceiling critical for AI coding assistants?

Enforces strict transaction-scoped memory allocation limits and row-projection caps on PostgreSQL 17 SQL/JSON JSON_TABLE queries. Deeply nested JSON path evaluations and unbounded NESTED PATH clauses expand combinatorially in backend process memory, requiring explicit SET LOCAL work_mem boundaries and deterministic pagination to prevent backend Out-Of-Memory (OOM) process termination and connection drops. 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 JSON_TABLE Queries with Deeply Nested Paths Over Exhaustible Connection Pools) 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