Konstantin Knizhnik 8bb4a13192 Do not materialize null images in PS (#5979) ...

## Problem

PG16 is writing null images during relation extension.
And page server implements optimisation which replace WAL record with
FPI with page image.
So instead of WAL record ~30 bytes we store 8kb null page image.
Ans this image is almost useless, because most likely it will be shortly
rewritten with actual page content.

## Summary of changes

Do not materialize wal records with null page FPI.
 
## 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>

2023-12-12 14:23:45 +02:00

..

benches

pageserver: refactor TenantId to TenantShardId in Tenant & Timeline (#5957)

2023-11-29 14:52:35 +00:00

ctl

pagectl: add subcommand to rewrite layer file summary (#5933)

2023-11-30 11:34:30 +00:00

src

Do not materialize null images in PS (#5979)

2023-12-12 14:23:45 +02:00

test_data

Add walingest test (#5892)

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

Cargo.toml

refactor: use serde for TenantConf deserialization Fixes: #5300 (#5310)

2023-11-30 12:47:13 +02:00