nautechsystems/nautilus_trader · error · anyhow::Error

Failed to batch insert into pool_tick table: {e}

Error message

Failed to batch insert into pool_tick table: {e}

What it means

Raised when a batched UNNEST INSERT of pool ticks (fee-growth-outside values, initialized flags, last-updated blocks) into the `pool_tick` table fails. The sqlx execution error is wrapped with this message; the tick batch is not persisted.

Source

Thrown at crates/adapters/blockchain/src/cache/database.rs:2314

                last_updated_block = EXCLUDED.last_updated_block
           ",
        )
        .bind(chain_id as i32)
        .bind(snapshot_block as i64)
        .bind(snapshot_transaction_index as i32)
        .bind(snapshot_log_index as i32)
        .bind(&pool_identifiers[..])
        .bind(&tick_values[..])
        .bind(&liquidity_grosses[..])
        .bind(&liquidity_nets[..])
        .bind(&fee_growth_outside_0s[..])
        .bind(&fee_growth_outside_1s[..])
        .bind(&initializeds[..])
        .bind(&last_updated_blocks[..])
        .execute(&self.pool)
        .await
        .map(|_| ())
        .map_err(|e| anyhow::anyhow!("Failed to batch insert into pool_tick table: {e}"))
    }

    /// Updates the initial price and tick for a pool.
    ///
    /// # Errors
    ///
    /// Returns an error if the database update fails.
    pub async fn update_pool_initial_price_tick(
        &self,
        chain_id: u32,
        initialize_event: &InitializeEvent,
    ) -> anyhow::Result<()> {
        sqlx::query(
            "
            UPDATE pool
            SET
                initial_tick = $4,
                initial_sqrt_price_x96 = $5

View on GitHub (pinned to 18893faf8b)

Solutions

1. Read the `{e}` suffix for the exact sqlx/PostgreSQL error
2. Use ON CONFLICT (pool_identifier, tick_idx) DO UPDATE for idempotent tick upserts
3. Ensure all bound arrays have equal lengths
4. Run migrations to align the pool_tick schema
5. Check connectivity/pool health and retry transient failures

Example fix

// before
.map_err(|e| anyhow::anyhow!("Failed to batch insert into pool_tick table: {e}"))
// after: upsert for idempotency and add context
// INSERT ... ON CONFLICT (pool_identifier, tick_idx) DO UPDATE SET ...
.map_err(|e| anyhow::anyhow!("Failed to batch insert into pool_tick table (rows={}): {e}", tick_idxs.len()))

fn validate_tick_batch(ticks: &[PoolTick]) -> anyhow::Result<()> {
    anyhow::ensure!(!ticks.is_empty(), "empty tick batch");
    anyhow::ensure!(ticks.iter().all(|t| t.last_updated_block > 0), "invalid block");
    Ok(())
}

fn is_initialized_tick(t: &PoolTick) -> bool { t.initialized }

if let Err(e) = insert_pool_ticks(&ticks).await {
    if e.to_string().contains("duplicate key") {
        tracing::debug!("ticks already present, upserting");
        upsert_pool_ticks(&ticks).await?;
    } else { return Err(e.into()); }
}

When it happens

Trigger: Executing the batch tick insert (`.bind(&fee_growth_outside_1s[..])`, `.bind(&initializeds[..])`, `.bind(&last_updated_blocks[..])`, `.execute(&self.pool)`) when Postgres rejects it: PK/unique conflict on (pool, tick_idx), type mismatch on growth values, array-length mismatch, or connection loss.

Common situations: Re-inserting ticks already stored from a prior snapshot (unique conflicts); u256-formatted growth strings not fitting numeric columns; missing migrations; dropped connections during long indexing batches.

Related errors

• Failed to batch insert into pool_fee_collect table: {e}
• Failed to batch insert into pool_flash_event table: {e}
• Failed to batch insert into pool_fee_protocol_update_event t
• Failed to batch insert into pool_fee_protocol_collect_event
• Failed to batch insert into pool_position table: {e}

AI-assisted analysis of nautechsystems/nautilus_trader@18893faf8b (2026-09-08). Data as JSON: /api/errors/d7c9b618f3a7d45c. Report an issue: GitHub.