It’s rather difficult to determine what your problem might be without some details about your environment, but if you database is growing so rapidly, there’s a possibility that the former DBA might have turned off autovacuuming and your’re now experiencing db bloat. Find your postgresql.conf file and look in it for the word autovacuum and see if it is set to off. If so, turn it back on. Your database will not reclaim the disk space, but if you can spare some downtime, a “vacuum full” can do wonders. Be advised that vacuum full locks tables for it’s exclusive use, so you do not want to use it during regular hours.
But that’s about all I can suggest without more details.
—
Jay
Sent from my iPad
On Apr 21, 2020, at 7:40 PM, Jesse Josserand <jesse.josserand@gmail.com> wrote:
I apologize in advance for bothering you, but I've not been able to get answers from the community by searches I've done, nor have I figured out how to post a question there.
I'm working for a gov't entity here in Mississippi and while I have extensive Oracle and MySQL experience, as well as Linux admin experience (which is what I was hired for), I've been given PostgreSQL DBA responsibilities since the last DBA quit abruptly (probably due to poor architecture and documentation here -- another thing I'm resolving).
I'm having serious space issues in a production environment and psql commands and queries are not helping me isolate it nor determine the root cause... possibly due to my naivete.
Would you be so kind as to give me some insight as to how to best determine what is growing to fast and why? I have a 20G disk that recently was increased to 40G and am now in less than 3 months almost out of space there again.
Yours truly,
Jesse Josserand, CTO
Direct Phone: 760-566-7866Business Phone/Fax: 855-236-5550
Owner, Sr. Consultant, Webmaster
All Divisions of ITWSLLC™