Ask HN: Will transaction ID wraparound be fixed in Postgres?

Ive read quite a bit about this and it seems a serious problem.

Will it ever be totally fixed or is it an un fixable problem for some reason?