[google-cloud-sql-discuss] Re: Postgres Vacuum problem

The NULL values from the select * from pg_stat_progress_vacuum is a known issue[1] which is why the are no visible results as to the progress of the vacuum. Please note that the process may be able to stopped with the function pg_cancel_backend(pid int) which cancels a backend's current query. You can execute this against another backend that has exactly the same role as the user calling the function. In all other cases, you must be a superuser which is not supported by Cloud SQL[3]. 

It seems you can truncate the table which is probably faster then vacuuming to reclaim that disk space though it is unclear if you can do it while vacuuming on the table is occurring. 

Finally if the above options do not work I suggest opening a private issue tracker[5] and provide your project id and the instance name of the effected instance but it is generally advised you try to either cancel/restart the vacuum yourself first. 

[1] https://issuetracker.google.com/146420099

[2] https://www.postgresql.org/docs/9.3/functions-admin.html

[3] https://cloud.google.com/sql/docs/postgres/users#superuser_restrictions

[4] https://www.postgresql.org/docs/9.1/sql-truncate.html

[5] https://issuetracker.google.com/issues/new?component=491274&template=1161130

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/ac5bc040-a846-4b3a-8683-d03fdbb8dd40%40googlegroups.com.