Context

Disaggregated storage is intended to run with

precise_checkpoint=true

, but the option currently defaults to

false

. It is therefore easy for a test or application to use fuzzy checkpoint semantics unintentionally.

Making precise checkpoints a hard requirement is not yet practical because the disaggregated-storage Python hook applies disaggregated storage across a broad set of tests that cannot all run with precise checkpoints today.

Proposal

Emit a once-per-connection warning when disaggregated storage is configured with

precise_checkpoint=false

. This provides an intermediate safeguard without rejecting existing configurations.

Python Test Behavior

• Explicit disaggregated-storage tests should fail on the unexpected warning, exposing configurations that omitted

  precise_checkpoint=true

  .

• Straightforward explicit tests should be updated to enable precise checkpoints.
• The disaggregated-storage Python hook should suppress only this known warning until its broader test coverage can use precise checkpoints.
• Other applications should continue opening successfully while receiving the warning.

Acceptance Criteria

• WiredTiger emits the warning once when a disaggregated connection opens without precise checkpoints.
• No warning is emitted when

  precise_checkpoint=true

  .

• The disaggregated-storage Python hook suppresses only this warning.
• Explicit disaggregated Python tests either enable precise checkpoints or deliberately expect the warning.
• Relevant Python tests and

  dist/s_fast

  pass.

Follow-up

Keep

FIXME-WT-14721

as the tracking item for eventually making precise checkpoints mandatory for disaggregated storage.