There is no point in trying to prevent pg_dump from overwriting a postgres executable when there are thousands of other ways to do that, if you're foolish enough to not be more careful with file permissions.
right. The responsibility for file caution and proper permissions rests with the user.
