iotaledger / iota / 16738220365

65%

Build Type

push

github

Committed by web-flow

Commit Message

fix(iota-indexer): Batch insert backfilled data to respect PostgreSQL's parameter limit (#8084)

# Description of change

This PR fixes an issue where backfill tasks fail due to exceeding
PostgreSQL's limit of 65,535 parameters per query.

Previously, the insertion logic didn't batch inserts, causing failures
when a checkpoint produced too many rows. The fix introduces batching
logic that splits inserts into smaller chunks, ensuring the total
parameters per query remain within the postgres limit.

## Links to any relevant issues

Fixes https://github.com/iotaledger/iota/issues/8083

## How the change has been tested

Make sure to provide instructions for the maintainer as well as any
relevant configurations.

- [X] Basic tests (linting, compilation, formatting, unit/integration
tests)
- [ ] Patch-specific tests (correctness, functionality coverage)

I was testing backfilling of the table with the failing checkpoint
(alphanet) and it can proceed as expected.

### Infrastructure QA (only required for crates that are maintained by
@iotaledger/infrastructure)

Not relevant for this patch. This PR doesn't touch migration objects or
synchronization of the indexer.

- [ ] Synchronization of the indexer from genesis for a network
including migration objects.
- [ ] Restart of indexer synchronization locally without resetting the
database.
- [ ] Restart of indexer synchronization on a production-like database.
- [ ] Deployment of services using Docker.
- [X] Verification of API backward compatibility.

### Release Notes

- [ ] Protocol:
- [ ] Nodes (Validators and Full nodes):
- [ ] Indexer:
- [ ] JSON-RPC:
- [ ] GraphQL:
- [ ] CLI:
- [ ] Rust SDK:
- [ ] REST API:

Run Details

0 of 7 new or added lines in 1 file covered. (0.0%)

1565 existing lines in 28 files now uncovered.

235447 of 359173 relevant lines covered (65.55%)

2337432.54 hits per line