Every modern database system provides functionality to make sure that the system can survive a crash in case something goes wrong or in case somebody pulls the plug. This is true for filesystems and database systems alike.
PostgreSQL also provides a means to ensure that a crash cannot harm the data integrity or the data itself. It is guaranteed that if the power cuts out, the system will always be able to come back up again and do its job.
The means to provide this kind of security is called write ahead log (WAL) or xlog. The idea is to not write into the data file directly, but instead write to the log first. Why is that important? Imagine you are writing some data:
INSERT INTO data ... VALUES ('12345678');
Suppose data was written directly to the data file. If the operation fails somewhere in the middle, the data file would be corrupted. It might contain half written...