This is a known issue, also see:
A new release needs to be cut, which will happen when the feat/db branch gets merged back into main. There are a few blockers still for that. This is from @tienson in the Logseq Discord server:
There’re a few todos we want to be done before cutting a desktop release for the db version:
- Performance improvements, especially for app start time and large tables, this should be done in a few days.
- Markdown and EDN export support, this should be done in weeks.
- Test to ensure we don’t introduce regression bugs for file graphs before merging the db branch to the master branch, I don’t have an estimated date for this one.