A single database file an architecture where all of the space lives within one or a small set of physical OS files.
E.g.instead of having operating system level files for each table, and index, it is all stuffed within a single file.
Thisis not important for big database systems that are professionally managed like the typical PostgreSQL installation.
However, it is hugely important for embedded type scenarios. An example is something like Quicken. Its database is
allwithin a single file (foo.qdf IIRC), which is awesome. Having a single housing eliminates an entire class of user
errors,and is a big win from a support perspective. The classic user screw up is a botched restore, where a user
restoresall of the data files (*.dat) but leaves all of the index files (*.idx) because he didn't know what they were.
Supportguys get this kind of incident all the time...
I haven't a clue why the authors listed PG (and the others) a having the feature.
-----Original Message-----
From: Tino Wildenhain [mailto:tino@wildenhain.de]
And whats: "Single Database File"? And why does PG have it?
Whats the point in havig it? ;)