Yes! The solution basically is:
to avoid this just run db:seed_fu before you backup or upgrade Postgres
.