This could be for 2 reasons:
-User of database (login role) without enough permissions.
In this case, check if the user, for example "postgres", have all the controls and privileges active.
-If localhost, check your antivirus, Twice.
Statistics made by postgresql might be considered as a virus movement by many antiviruses (ESET in my case), is a false positive, the only solution is to locate the directory of the database (like \PostgreSQL\9.3\data) and create am exception to that directory in your antivirus software.
As you can see, this second option is not related to the database code it self.
Hope this help you.