Portability of dumps

Question

PostgreSQL

Before 2002 I used postgres. Now I use only for OSM. But, the rock is related to the fact that
1. database dumps had to be processed manually when importing into a new version
2. not infrequently, when updating the postgres version, triggers or indexes were bent
3. during the vacuum, it was impossible to make a select
forced me to switch to mysql + middleware.

Question.
1. Are there still such problems?
2. How difficult it is to restore the database after hardware errors, power outages, etc. (the base is non-replicable).

PS I'm interested in practice (now, judging by what I read, there are no such problems in principle. But even then there were fewer mats for postgres than for muscle or oracle).

Answer 1

1.1. Shield?
1.2. I have not heard of this, although I did not have to upgrade particularly complex databases.
1.3. The vacuum is no longer needed.
2. Well, there should be a backup anyway. For all the time I remember only one case when I had to repair the database. Honestly, I do not remember what was the matter, but somehow it was easily solved.
In general - use on health. I always prefer Postgres whenever possible, I have never regretted it.