Walkthrough

Changes introduce per-entry execution context isolation in PostgreSQL wire protocol batch processing. PGPipelineEntry now maintains individual SqlExecutionContext and BindVariableService instances, while PGConnectionContext routes pipeline operations through entry-scoped contexts instead of the shared global sqlExecutionContext.

Changes

Sequence Diagram

sequenceDiagram
    participant Client
    participant PGConnectionContext
    participant PGPipelineEntry
    participant Engine

    Note over Client,Engine: Batched Queries with Bound Parameters

    Client->>PGConnectionContext: Send batch (Query 1 + params=1, Query 2 + params=2, ...)
    
    PGConnectionContext->>PGPipelineEntry: Create entry N (entryExecutionContext initialized)
    PGPipelineEntry->>PGPipelineEntry: BindVariableService created per entry
    
    PGConnectionContext->>PGPipelineEntry: msgExecute(entryExecutionContext)
    PGPipelineEntry->>Engine: execute(entryExecutionContext with params=N)
    Engine-->>PGPipelineEntry: Result for Query N
    PGPipelineEntry->>PGConnectionContext: Return result
    
    Note over PGPipelineEntry: Parameters isolated per entry
    
    alt Next entry in batch
        PGConnectionContext->>PGPipelineEntry: Create entry N+1 (fresh entryExecutionContext)
        PGPipelineEntry->>PGPipelineEntry: New BindVariableService created
        PGConnectionContext->>PGPipelineEntry: msgExecute(entryExecutionContext)
        PGPipelineEntry->>Engine: execute(entryExecutionContext with params=N+1)
        Engine-->>PGPipelineEntry: Result for Query N+1
    end
    
    PGConnectionContext->>Client: Return all results in order

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

• Context lifecycle verification: Ensure per-entry SqlExecutionContext and BindVariableService initialization and cleanup are thread-safe and occur at correct lifecycle points. Verify no leaks on error paths.
• PGPipelineEntry constructor and close methods: Confirm DenyAllSecurityContext and BindVariableServiceImpl initialization align with security model and resource management patterns.
• Call site updates in PGConnectionContext: Verify all msgExecute, msgSync, and postCompile invocations correctly route through getEntryExecutionContext() and no legacy sqlExecutionContext references remain in critical paths.
• Batch parameter isolation semantics: Confirm that per-entry contexts properly isolate bound variables across sequential batch commands, preventing cross-entry parameter leakage.

Suggested reviewers

• puzpuzpuz

Pre-merge checks and finishing touches

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

@coderabbitai review