Konstantin Knizhnik f3d7d23805 Some small WAL records can write a lot of data to KV storage, so perform checkpoint check more frequently (#6639) ...

## Problem

See
https://neondb.slack.com/archives/C04DGM6SMTM/p1707149618314539?thread_ts=1707081520.140049&cid=C04DGM6SMTM

## Summary of changes


Perform checkpoint check after processing `ingest_batch_size` (default
100) WAL records.

## Checklist before requesting a review

- [ ] I have performed a self-review of my code.
- [ ] If it is a core feature, I have added thorough tests.
- [ ] Do we need to implement analytics? if so did you add the relevant
metrics to the dashboard?
- [ ] If this PR requires public announcement, mark it with
/release-notes label and add several sentences in this section.

## Checklist before merging

- [ ] Do not forget to reformat commit message to not include the above
checklist

---------

Co-authored-by: Konstantin Knizhnik <knizhnik@neon.tech>

2024-02-07 08:47:19 +02:00

..

benches

pageserver: make walredo shard-aware

2024-01-03 14:22:40 +00:00

client

Download SLRU segments on demand (#6151)

2024-01-31 21:39:18 +02:00

ctl

integrate tokio-epoll-uring as alternative VirtualFile IO engine (#5824)

2024-01-26 09:25:07 +01:00

pagebench

pagebench: actually implement --num_clients (#6640)

2024-02-06 10:34:16 +01:00

src

Some small WAL records can write a lot of data to KV storage, so perform checkpoint check more frequently (#6639)

2024-02-07 08:47:19 +02:00

test_data

Add walingest test (#5892)

2023-11-28 12:50:53 -05:00

Cargo.toml

feat(walredo): use posix_spawn by moving close_fds() work to walredo C code (#6574)

2024-02-01 22:38:34 +01:00