Cosimo Streppone <cosimo@streppone.it> writes:
> Is there an estimate time for this issue to be resolved?
Approximately never. It's a fundamental feature of Postgres' design.
As noted by Dennis, you can look at the pg_class statistics if a recent
estimate is good enough, or you can build user-level tracking tools if
you'd rather have fast count(*) than concurrent update capability. But
don't sit around waiting for the developers to "fix this bug", because
it isn't a bug and it isn't going to be fixed.
regards, tom lane