They all have their purpose.
PostgreSQL is free.
It is also on par with Oracle
When it comes to GIS, you won't find many of these 'out of the box' features that come with PostgreSQL
On PostgreSQL itself:
I have had extensive experience with Oracle DBMS used in one of the most data intense environments (Telecommunications)
It is still one of the best available for most any extremely high volume data task, but only large corporations can afford
it. PostgreSQL can come close, and maybe even match it's performance, can run on as many cores as you can give it, and
is free.
I'm a fan, and have been for a long time.
Sqlite is very good, and I use it. One thing I especially like is the one file for everything.
I haven't ever tried to use it with extremely high volume data.
PostgreSQL is free.
It is also on par with Oracle
When it comes to GIS, you won't find many of these 'out of the box' features that come with PostgreSQL
- Support for GeoJSON and KML
- Geometry-processing functions that go far beyond basic geometric operations
- 3D and topology support
- Operations (over 150 of them) for working with raster and vectors in tandem
- Many conversion operations for converting between raster and vector data.
On PostgreSQL itself:
- it is the most advanced open source database, period.
- It's speed and functionality is on par with Oracle.
- It can and does power databases terabytes in size.
- It is extensible.
I have had extensive experience with Oracle DBMS used in one of the most data intense environments (Telecommunications)
It is still one of the best available for most any extremely high volume data task, but only large corporations can afford
it. PostgreSQL can come close, and maybe even match it's performance, can run on as many cores as you can give it, and
is free.
I'm a fan, and have been for a long time.
Sqlite is very good, and I use it. One thing I especially like is the one file for everything.
I haven't ever tried to use it with extremely high volume data.