TL;DR: `[tasklist] ### Tasks - [ ] YOUR_HOST.com/neondatabase/neon/issues/7236 - [ ] YOUR_HOST.com/neondatabase/neon/pull/8162 - [x] Shutdown records, or do we need to do a checkpoint at compute shutdown? - [ ] YOUR_HOST.com/neondatabase/cloud/issues/14903 - [ ] YOUR_HOST.com/neondatabase/cloud/issues/10800 - [ ] ## When to use You hit exactly this: Epic: stabilize physical replication in Epic. ## When not to use A different error, or the same symptom in a different tool.

TL;DR: [ololobus (maintainer)]: > What actually you mean by "fully static ROs"? I meant that we will start static computes pinned to specific LSN. Right now, it's turned off in cplane, so for some

## Fix
1. [ololobus (maintainer)]: > What actually you mean by "fully static ROs"?
   Expected: this specific failure stops.
2. I meant that we will start static computes pinned to specific LSN.
   Expected: this specific failure stops.
3. Right now, it's turned off in cplane, so for some.
   Expected: this specific failure stops.
4. `branch@LSN`.
   Expected: this specific failure stops.

## Details
[ololobus (maintainer)]: > What actually you mean by "fully static ROs"? I meant that we will start static computes pinned to specific LSN. Right now, it's turned off in cplane, so for some `branch@LSN` compute, we first need to create a temporary branch at this LSN and then start a 'normal' RO on it. IIRC, the problem was with the races with GC. Once we have leases, we can turn on static computes usage in cplane again Context: GitHub issue neondatabase/neon#6211 (closed, 97 comments): # Summary Original issue we hit was ``` page server returned error: tried to request a page version that was garbage collected. requested at C/1E923DE0 gc cutoff C/23B3DF00 ``` but then the scope grew up quickly. This is the Epic to track main physical replication work `` `[tasklist] ### Tasks - [ ] YOUR_HOST.com/neondatabase/neon/issues/7236 - [ ] YOUR_HOST.com/neondatabase/neon/pull/8162 - [x] Shutdown records, or do we need to do a checkpoint at compute shutdown? - [ ] YOUR_HOST.com/neondatabase/cloud/issues/14903 - [ ] YOUR_HOST.com/neondatabase/cloud/issues/10800 - [ ]

## When to use
You hit exactly this: Epic: stabilize physical replication in Epic.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
Epic.