@cfxlabsinc/b2b-services
    Preparing search index...

    Variable ACCOUNT_TRANSACTION_INSERT_CHUNK_SIZEConst

    ACCOUNT_TRANSACTION_INSERT_CHUNK_SIZE: 100

    Rows per insert … values for solana_account_transaction.

    RDS Proxy pins a session once a statement's TEXT passes 16,384 bytes. Bind VALUES are free but bind PLACEHOLDERS are not: eight columns of $n cost ~56 bytes of text per row, so an unbounded multi-row insert crosses the limit around 290 rows however cheap each row is. Chunking is what makes the bound a property of the code rather than of whatever the chain hands us — a single Solana transaction touching enough (owner, mint) pairs would otherwise pin the writer connection for the rest of the session.

    100 rows renders ~5.8KB, comfortably clear. Prod's widest transaction across the last ~70,000 produced 13 rows, so this is a guard rail rather than a throughput knob.

    • test/solanaAccountTransactionStatementSize.test.ts
    • docs/runbooks/rds-proxy-pinning.md