Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libsql/replication: Handle remote errors #409

Merged
merged 1 commit into from
Sep 20, 2023
Merged

Conversation

LucioFranco
Copy link
Contributor

No description provided.

@LucioFranco LucioFranco added this pull request to the merge queue Sep 20, 2023
Merged via the queue into main with commit 56382af Sep 20, 2023
4 checks passed
@LucioFranco LucioFranco deleted the lucio/fix-todos2 branch September 20, 2023 15:50
@MarinPostma MarinPostma mentioned this pull request Oct 17, 2023
github-merge-queue bot pushed a commit that referenced this pull request Oct 17, 2023
Secure mode has a performance and overhead penalty,
and we don't really need to be robust against memory reuse attacks
in sqld.
Simple measurements show that secure mode can bump resident memory
usage as much as 250%, plus there's the cpu cost of encrypting
freelists and other features that they offer.
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.

None yet

1 participant