Skip to content

Conversation

def-
Copy link
Contributor

@def- def- commented Oct 6, 2025

Noticed in https://github.com/MaterializeInc/database-issues/issues/9754

Maybe we want to just change the default in the code.

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

@def- def- requested a review from teskje October 6, 2025 13:22
@teskje
Copy link
Contributor

teskje commented Oct 6, 2025

There is a related PR here: #33622. I think the concerns are roughly the same, namely whether or not we can expect emulator users to use swap now. Though in contrast to self-managed we aren't dependent on cloud provider support here, it's probably just a question of documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants