Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jR2eN-0000mv-83 for pgsql-admin@arkaria.postgresql.org; Tue, 21 Apr 2020 23:49:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jR2dq-0001WL-0t for pgsql-admin@arkaria.postgresql.org; Tue, 21 Apr 2020 23:49:26 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jR2dp-0001WD-If for pgsql-admin@lists.postgresql.org; Tue, 21 Apr 2020 23:49:25 +0000 Received: from mail-qv1-xf36.google.com ([2607:f8b0:4864:20::f36]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jR2di-0001jr-Q2 for pgsql-admin@lists.postgresql.org; Tue, 21 Apr 2020 23:49:24 +0000 Received: by mail-qv1-xf36.google.com with SMTP id v10so79670qvr.2 for ; Tue, 21 Apr 2020 16:49:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=b3sLNpFyReACmULnIS9IAu1VjV3OvCG0dIMqZspNoXs=; b=R7rceKjRV/EbfzdZTVrhptd5sL1dcfGOululsbuv7lvfKJZwEiJ2VZ6C5Kgjm7XmCy ZQVwpemB8yO7NqfPYYOvIairvQdqVUqy0GLcdqIBieUBH8rEREIHV47pAG9dvDCUxxwG 9A4gZtegBHCkUBJvYreoKprqLSN8EfvfQ4LP7pONHT9Esh55tLNwkKm0U43oCOKTTg+q f2GoxDnhVsn28jUcQk/xw/gGa59g8KhCILi2Qldg5p1npS5rIrdrE6IblGo+zFF2Mkvp L9Sq/+fspw9/DRpMEwatB+f3acBK4T3GtUWuaOFqBHh9VFLJzCov2qeyrdK6TeTv2nvs H/2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=b3sLNpFyReACmULnIS9IAu1VjV3OvCG0dIMqZspNoXs=; b=dOD5bTttjK+jHlfPMCaFBNCQ8iE6dBy2lfzw3m0kmTV6Knv/NCsAzBGXTn+tcwBEpF 0suDq8JnCeDUb079DptFfetV5Q00GYH+XAs28F+/X3iZtsDuSxHC7qraKnj2ewz5mqDE ZeXL/AcigT6XIGrtSV3yamFq6rrA1+xAP69r6tQSlK66OgfNEpN8j9mNELjlOhZpIkOQ 3nxu735YOYATqkBozgUymjWS23cLTWycPIMW1oq33Ra2qJqTb2PxDilusHNG431A0Tfz zUMs8iwQSBoZS/xVb3Py4+4Mm2hQe7urQWHb/UbYMT1Fv9HHAdRgmt39iNUHDjzAIxzg yxTA== X-Gm-Message-State: AGi0PuZvUByzgx3xr0jW0jT92oxbDPIWBULbW4EFcl8i+Mcihlk7GUUt ZJ2Cy59F+hF372lKFj8PWgNO7wD+ X-Google-Smtp-Source: APiQypJ4C6iY+v7msrGhtnTGFKlgepcX6iK+fqpip1TS9UM+vQT6roY2bCVhqzULgMJ1an2b+rhUaw== X-Received: by 2002:ad4:458a:: with SMTP id x10mr22739747qvu.199.1587512957165; Tue, 21 Apr 2020 16:49:17 -0700 (PDT) Received: from ?IPv6:2603:9000:f609:a03d:d9cf:d178:8d5:86e1? ([2603:9000:f609:a03d:d9cf:d178:8d5:86e1]) by smtp.gmail.com with ESMTPSA id q15sm2713103qkn.100.2020.04.21.16.49.16 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 21 Apr 2020 16:49:16 -0700 (PDT) Content-Type: multipart/alternative; boundary=Apple-Mail-7B21378F-08D7-44D7-BDC3-AEFD68642F11 Content-Transfer-Encoding: 7bit From: John Scalia Mime-Version: 1.0 (1.0) Subject: Re: Newbie needs help with space issue Date: Tue, 21 Apr 2020 19:49:15 -0400 Message-Id: <3FDE1750-9085-4A7D-9F09-E8141956D259@gmail.com> References: Cc: pgsql-admin@lists.postgresql.org In-Reply-To: To: Jesse Josserand X-Mailer: iPad Mail (17D50) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --Apple-Mail-7B21378F-08D7-44D7-BDC3-AEFD68642F11 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable It=E2=80=99s rather difficult to determine what your problem might be witho= ut some details about your environment, but if you database is growing so ra= pidly, there=E2=80=99s a possibility that the former DBA might have turned o= ff autovacuuming and your=E2=80=99re now experiencing db bloat. Find your po= stgresql.conf file and look in it for the word autovacuum and see if it is s= et to off. If so, turn it back on. Your database will not reclaim the disk s= pace, but if you can spare some downtime, a =E2=80=9Cvacuum full=E2=80=9D ca= n do wonders. Be advised that vacuum full locks tables for it=E2=80=99s excl= usive use, so you do not want to use it during regular hours. But that=E2=80=99s about all I can suggest without more details. =E2=80=94 Jay Sent from my iPad > On Apr 21, 2020, at 7:40 PM, Jesse Josserand w= rote: >=20 > =EF=BB=BF > I apologize in advance for bothering you, but I've not been able to get an= swers from the community by searches I've done, nor have I figured out how t= o post a question there. >=20 > I'm working for a gov't entity here in Mississippi and while I have extens= ive Oracle and MySQL experience, as well as Linux admin experience (which is= what I was hired for), I've been given PostgreSQL DBA responsibilities sinc= e the last DBA quit abruptly (probably due to poor architecture and document= ation here -- another thing I'm resolving). >=20 > I'm having serious space issues in a production environment and psql comma= nds and queries are not helping me isolate it nor determine the root cause..= . possibly due to my naivete. >=20 > Would you be so kind as to give me some insight as to how to best determin= e what is growing to fast and why? I have a 20G disk that recently was incre= ased to 40G and am now in less than 3 months almost out of space there again= . >=20 > Yours truly, > Jesse Josserand, CTO > IT Web Services, LLC and=20 > Ace Consulting Solutions, Inc. > Direct Phone: 760-566-7866 > Business Phone/Fax: 855-236-5550 > Owner, Sr. Consultant, Webmaster > Josserand Ace ConsultinG=E2=84=A2 (JacG=E2=84=A2) 800-698-1030, > SalesRepsNow.Com (888-272-8885), and > World Profit Club Network Marketing Alliance (WPCNMA)=C2=AE (800-980-8233)= . > All Divisions of ITWSLLC=E2=84=A2 --Apple-Mail-7B21378F-08D7-44D7-BDC3-AEFD68642F11 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable It=E2=80=99s rather difficult to  dete= rmine what your problem might be without some details about your environment= , but if you database is growing so rapidly, there=E2=80=99s a possibility t= hat the former DBA might have turned off autovacuuming and your=E2=80=99re n= ow experiencing db bloat. Find your postgresql.conf file and look in it for t= he 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 downtim= e, a =E2=80=9Cvacuum full=E2=80=9D can do wonders. Be advised that vacuum fu= ll locks tables for it=E2=80=99s exclusive use, so you do not want to use it= during regular hours.

But that=E2=80=99s about all I can= suggest without more details.
=E2=80=94
Jay

Sent from my iPad

On Apr 21, 2020, at 7:40 PM, Jesse Josserand <jesse.josserand@gmai= l.com> wrote:

=EF=BB=BF
I apologize in advance for bothering you= , but I've not been able to get answers from the community by searches I've d= one, 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 extensi= ve Oracle and MySQL experience, as well as Linux admin experience (which is w= hat I was hired for), I've been given PostgreSQL DBA responsibilities since t= he last DBA quit abruptly (probably due to poor architecture and documentati= on here -- another thing I'm resolving).

I'm having= serious space issues in a production environment and psql commands and quer= ies are not helping me isolate it nor determine the root cause... possibly d= ue to my naivete.

Would you be so kind as to give m= e 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.
<= div dir=3D"ltr">

Yours truly,
Jesse Josserand, CTO
Direct Phone: 760-566-7866<= /span>
Business Phone/Fax: 855-236-5550
Owner, Sr. Consultant, Webmaster
SalesRepsNow.Com&nbs= p;(888-272-8885), and
World Profit= Club Network Marketing Alliance (WPCNMA)=C2=AE (800-980-8233).
All Divisions of  ITWSLLC=E2=84= =A2
=
= --Apple-Mail-7B21378F-08D7-44D7-BDC3-AEFD68642F11--