I mean, you’re not wrong about the facts, but it’s also pretty trivial to migrate the data from SQLite into a separate Postgres server later, if it turns out you do need those features after all. But most of the time, you don’t.

▲

pdhborges 13 hours ago | parent [-]

I bet that takes more time than the 5 extra minutes you take to setup Postgres in the same box upfront.

▲

SpaceNoodled 5 hours ago | parent [-]

To export a database? Probably even faster. And that's ignoring the difference in performance.

	▲	pdhborges 5 hours ago \| parent [-]
		So you are migrating from Sqlite to Postgres because you need it. What is the state of your product when you need to do this migration? Is your product non trivial? Are you now dependent on particular performance characteristics of Sqlite? Do you now need to keep your service running 24/7? Accounting for all of that takes way more than 5 minutes. The only way to beat that is if you still have a toy product and you can just export the database and import it and pray that it all works as a migration strategy.