Does Render perform any garbage collection maintinence on the postgresql database?

I get an error when i try to run VACUUM FULL; on the remote psql database.

WARNING: skipping “pg_database” — only superuser can vacuum it

is there any alternative to reclaim storage occupied by dead tuples in the db?

thanks for any info,
-amsterdamAL

Hey,

You should be able to run ‘VACUUM [tablename]’ on a specific table as a non-superuser but auto-vacuum should do most of the job. Why do you feel the need to vacuum your database manually? Have you noticed an issue with auto-vacuum?

Jérémy.
Render Support, UTC+3

Hi Jeremy, thanks for the info…

The VACUUM [tablename] command did work :+1:
However, since my database is new, and has very little data at the moment, the VACUUM command didn’t reduce the size.

From the 1GB total size, I’m using 6.52% (62Mb)

after poking around and checking table sizes, i realized the 62Mb was due to other databases (postgres, template0 and template1) and probably overhead.

Also, so i know in the future, is auto-vacuum handled by render maintenance?
or something i have to setup in a script or psql command line?

thanks again for the help.
-amsterdamAL

Hey,

We’re not running any special vacuum operations; we’re relying on the built-in capabilities of Postgres for that. Postgres is designed to handle this by default, and we haven’t disabled this feature. If you’re encountering any issues related to vacuuming, please inform us.

Jérémy.
Render Support, UTC+3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.