Konstantin Knizhnik e58f264a05 Increase inmem SMGR size for walredo process to 100 pagees (#10937) ...

## Problem

We see `Inmem storage overflow` in page server logs:

https://neondb.slack.com/archives/C033RQ5SPDH/p1740157873114339

walked process is using inseam SMGR with storage size limited by 64
pages with warning watermark 32 (based ion the assumption that
XLR_MAX_BLOCK_ID is 32, so WAL record can not access more than 32
pages).

Actually it is not true. We can update up to 3 forks for each block
(including update of FSM and VM forks).

## Summary of changes

This PR increases inseam SMGR size for walled process to 100 pages and
print stack trace in case of overflow.

---------

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

2025-02-27 14:31:05 +00:00

..

neon

PS/Prefetch: Use a timeout for reading data from TCP (#10834)

2025-02-27 14:00:18 +00:00

neon_rmgr

Remove unused static function

2024-10-07 23:49:11 +03:00

neon_test_utils

Use smgrexists() instead of access() to enforce uniqueness of generated relfilenumber (#7992)

2024-07-23 18:41:55 +03:00

neon_utils

Be able to get number of CPUs (#3774)

2023-03-10 19:00:20 +02:00

neon_walredo

Increase inmem SMGR size for walredo process to 100 pagees (#10937)

2025-02-27 14:31:05 +00:00

.dir-locals.el

Copy editor config for the neon extension from PostgreSQL (#8009)

2024-06-11 23:19:18 +03:00

.editorconfig

Copy editor config for the neon extension from PostgreSQL (#8009)

2024-06-11 23:19:18 +03:00

typedefs.list

Refotmat pgxn code, add typedefs.list that was used

2022-09-14 08:14:05 +03:00