Documentation regarding Consistency

[ackava]

Can you please add some documentation about how to maintain consistency in terms of running it from browser?

1. Can multiple PGLite easily access single storage (IndexedDB)?
2. Will it corrupt the data? Do we need any external locking mechanism?

[samwillis]

Good idea, we should document this better.

For quick context, PGlite is Postgres in "single user mode". There is no support for concurrent connections and you are like to corrupt the database if you open it multiple times at once.

The PGliteWorker helps you to open only a single instance and share it across browser tabs.

[0xOlias]

Related question - is there any way to check if a target directory is currently in use by a PGlite instance?

It would be awesome if the PGlite constructor threw (or the waitReady promise rejected) with a descriptive error, e.g. "this dataDir is currently in use by another PGlite instance" rather than allow undefined behavior / data corruption. I'm using the Node.js filesystem, but I imagine this applies to the others as well.

I think this validation would be reasonable in either the init or initialSyncFs methods on the Filesystem interface.

pglite/packages/pglite/src/pglite.ts

Lines 345 to 346 in 5e39036

	// Sync the filesystem from any previous store
	await this.fs!.initialSyncFs()

[samwillis]

Hey @0xOlias

Yep, we should absolutely do this.

In the browser I think the best way is to implement it with WebLocks, for Node we should open and lock a file in the FS.