News for hackers. Stuff that matters.

A comment on Bluesky migrates from pg to single-tenant SQLite. Parent comment

Re:Bluesky migrates from pg to single-tenant SQLite by sinkwool on Monday November 06, 2023 @08:52PM (#38172146)
> Writers merely append new content to the end of the WAL file. Because writers do nothing that would interfere with the actions of readers, writers and readers can run at the same time. However, since there is only one WAL file, there can only be one writer at a time.

I think the OP meant that updates have to run sequentially.

[ Parent | on HN ]
Re:Bluesky migrates from pg to single-tenant SQLite by starcraft2wol on Monday November 06, 2023 @08:58PM (#38172200)
Which just means the lock happens at user scope in this case instead of per table or row. This limitation still causes so much confusion when it’s a completely reasonable design.
[ Parent | on HN ]
Re:Bluesky migrates from pg to single-tenant SQLite by mikrotikker on Tuesday November 07, 2023 @01:23AM (#38173826)
I've been importing data to sqlite databases running being actively written to for years. Just throws exception if the database is locked and I retry. Do 10k row batches, with a small sleep between. No issues. Helps if your use case doesn't really care about data being in order I guess.
[ Parent | on HN ]