Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

paritydb panics when used for light client #7125

Closed
dvc94ch opened this issue Sep 17, 2020 · 1 comment · Fixed by #7130
Closed

paritydb panics when used for light client #7125

dvc94ch opened this issue Sep 17, 2020 · 1 comment · Fixed by #7130

Comments

@dvc94ch
Copy link
Contributor

dvc94ch commented Sep 17, 2020

So we stopped using our custom sled db setup and noticed that it doesn't work.

The problem comes from optimizations being enabled for column::STATE which has col_id 1, which aren't valid when using the light client that has KEY_LOOKUP as col_id 1. As a workaround the optimizations can be disabled.
@bkchr
Copy link
Member

bkchr commented Sep 17, 2020

CC @arkpar

@arkpar arkpar mentioned this issue Sep 17, 2020
Merged
@ghost ghost closed this as completed in #7130 Sep 17, 2020
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix db initialization for light client paritytech/substrate
2 participants
@dvc94ch @bkchr