Should Ponder replace SQLite with PGlite (pglite.dev) as the dev database? 

Pros:
1) Less magic/astonishment ("wait, what database am I using rn?")
2) Simpler schema definition API (currently stuck with the subset of stuff that both PG and SQLite support)

Building ponder.sh. EVM, TypeScript, open-source enjoyer.

When you say as a "dev database" are you referring to local development?

Hi! My name is Daniel. I am building bountycaster.xyz

Ex Phantom, 0x Project engineer.

From Italy originally, currently live in NYC

Would opt for the same database in local and prod. With Docker nowadays, unless you are running something like Cassandra or Elasticsearch there is little to no downside in spinning up your local Postgres

docker run --name local-postgres -e POSTGRES_PASSWORD=mysecretpassword -p 5432:5432 -d postgres

I see, definitely a tricky one. i'd always bias towards a DB that is more maintained (sqlite3) however I do understand the annoyance of running 2 different databases in prod.

Are there specific features you are using for Postgres?

Yes. More precisely - what database is used the very first time someone runs Ponder on their local machine.

It needs to be in-process - if you had to start a PG server to get Ponder working, I estimate ~50% of current users would have churned at that step 🤷‍♂️