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?
The VACUUM [tablename] command did work
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?
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.