4 ms·
I can only think of three cases: 1) You need an embedded relational database with a small foot print. Here PostgreSQL cannot compete with SQLite. 2) You have
by jeltz 8y ago
I can only think of three cases:
1) You need an embedded relational database with a small foot print. Here PostgreSQL cannot compete with SQLite.
2) You have an application which does not support PostgreSQL.
3) You have petabytes worth of data. Here you want to look into something like Greenplum, a PostgreSQL fork.
- truth_seeker 8y agoPG works okay with Peta Bytes of data. Various types of indexes, Table partitioning and parallel query computation can help. Citus and other community extensions can help if you want to go distributed and fault tolerant
- jacques_chester 8y agoWorth noting that the Greenplum team are working to converge back to mainline.