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 1q0pBj-0003GX-Pp for pgsql-admin@arkaria.postgresql.org; Sun, 21 May 2023 19:57:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q0pBi-0001Ea-IN for pgsql-admin@arkaria.postgresql.org; Sun, 21 May 2023 19:57:54 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q0pBi-0001EM-4Z for pgsql-admin@lists.postgresql.org; Sun, 21 May 2023 19:57:54 +0000 Received: from mail-yw1-x1134.google.com ([2607:f8b0:4864:20::1134]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1q0pBa-001DsD-Ao for pgsql-admin@lists.postgresql.org; Sun, 21 May 2023 19:57:53 +0000 Received: by mail-yw1-x1134.google.com with SMTP id 00721157ae682-561a33b6d63so70705207b3.1 for ; Sun, 21 May 2023 12:57:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684699065; x=1687291065; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=0NOXd1Vh3yso7J36dEUskZqu5mp5sY0jpZeTpOGiCms=; b=j8w3SRVnk0XGwR2H4aRxZrnQn7wCXObJIxstu7X2DWd1smAzuzChBmLuAi0pg04wVT ct3h5j4Y/HjvKZqhEmxYTmtKbuBkymRmHOLQG8P+zQuCb1N9hPC+O6Dm9HQG9+n4sqxl 0F8jZEoqaXp7e2dSs/LMM8bZtyVPiGK3B4b6IEbCeTtTM4oPf46ljd+tY2SkFiFyB/Cw 4jL562+Ja3An9C7dmwnk0aMajhwI9oqxNBoeA3WaMwn//JZYwJuoFnzaRhpcZzWFDvSp opxWr+7z+/pFVPbzgwILRxogGpEgQpLbwFlK4GnQXTq2+HhC8QHAYKxmBTwNaic3xPYC /9RA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684699065; x=1687291065; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=0NOXd1Vh3yso7J36dEUskZqu5mp5sY0jpZeTpOGiCms=; b=YdWOKMpukcc+tNqjFPOpkPtnYDMVbwC0VqHxvTp8BUdxlQFoHOqhdDJz9HxMv2zTRv sUNxfX1KZGvY1m2yyDfKslMITl7GSBpDLz5METaMu0IEZQg0314WQOiKn1hORIzKasJH xSYjB+0IKxjMW3kRjaA9jza3WlGb3QtvZeLf7HQn+rmgm9jY/R5pHJzkACTmZ4O9aR3w 6NKiB/aRUSriQP9xUR5/idPYtztlVj/vjAcOYtnnm2sUoS2kz4RIYMB/g28MznXanhY4 257V40eacUMYFM4XA1KeyYWH1nyzJfxBdPckDorVljcems4iG7V8+BAzt7Cd1JFMBGqA /A8Q== X-Gm-Message-State: AC+VfDxyGzTqiJ1/k0fAoqYhFtKoqvkWRhEGbGh9hNPzvnme8wulCy+S 1QjuR2LopUXiEOjifkIcEEOWACfqb2k= X-Google-Smtp-Source: ACHHUZ4H70pe+z31QPFVyq6io/M3g32DnCsgd5djLMt6qYiCuj69jk1xaLaBLmQo4bFkPg8c+uQcQg== X-Received: by 2002:a0d:cc8c:0:b0:561:b2bf:ed98 with SMTP id o134-20020a0dcc8c000000b00561b2bfed98mr9326517ywd.36.1684699065025; Sun, 21 May 2023 12:57:45 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810:edd0:f41d:bc84:c44b? ([2600:1700:bd2c:b810:edd0:f41d:bc84:c44b]) by smtp.googlemail.com with ESMTPSA id z73-20020a0dd74c000000b00559d9989490sm1541753ywd.41.2023.05.21.12.57.44 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 21 May 2023 12:57:44 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------k9nhfq83FiWWlqH85BuezPtc" Message-ID: Date: Sun, 21 May 2023 14:57:43 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: RDS No free space Content-Language: en-US To: pgsql-admin@lists.postgresql.org References: <278448.1684689788@sss.pgh.pa.us> From: Ron In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------k9nhfq83FiWWlqH85BuezPtc Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 5/21/23 12:52, Lucio Chiessi wrote: > You can check if you having some strong queries that were generating a lot > of temp files, that will can eat all off free space. That was my first thought. > > On Sun, 21 May 2023 at 14:48 Wells Oliver wrote: > > I'm not too familiar with that. Can you point me in the direction of > some config settings and maybe queries to execute? > > On Sun, May 21, 2023 at 10:43 AM Jim Mlodgenski wrote: > > > > On Sun, May 21, 2023 at 1:38 PM Wells Oliver > wrote: > > So we run on RDS, and we clearly used up all of our > provisioned storage. However, I am baffled, and while I am > emailing our AWS support, I wondered if this list might point > me in some direction too. > > Our provisioned storage was 15TB. The size of our database -- > shown in pg_database -- is only 6TB. What in the world could > be using that remaining space? I am at a loss, that's a _ton_ > of space being used up. Is it some temporary allocation during > script execution (seems ginormous, impossible)? It it some WAL > log thing? > > > A fairly common cause of this is orphan replication slots so WAL > files are retained. Check > to see if there is an inactive slot that may be preventing the > files to be removed. > > > > -- > Wells Oliver > wells.oliver@gmail.com > > -- > > *Lucio Chiessi* > > Senior Database Administrator > > Trustly, Inc. > > M: +55 27 996360276 > > > > > > > > > PayWith*MyBank^® * is now part of***Trustly* > > > Please read our privacy policy *here > *on how we process your > personal data in accordancewiththeGeneral Data Protection Regulation(EU) > 2016/679 (the “GDPR”) and other applicable data protection legislation -- Born in Arizona, moved to Babylonia. --------------k9nhfq83FiWWlqH85BuezPtc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 5/21/23 12:52, Lucio Chiessi wrote:
You can check if you having some strong queries that were generating a lot of temp files, that will can eat all off free space.

That was my first thought.


On Sun, 21 May 2023 at 14= :48 Wells Oliver <we= lls.oliver@gmail.com> wrote:
I'm not too familiar with that. Can you poin= t me in the direction of some config settings and maybe queries to execute?

On Sun, May 21, 2023 = at 10:43=E2=80=AFAM Jim Mlodgenski <jimmy76@gmail.com> wrote:


On Sun, May 21,= 2023 at 1:38=E2=80=AFPM Wells Oliver <wells.oliver@gmai= l.com> wrote:
So we run on RDS, and we clearly used up all of our provisioned storage. However, I am baffled, and while I am emailing our AWS support, I wondered if this list might point me in some direction too.

Our provisioned storage was 15TB. The size of our database -- shown in=C2=A0pg_database --= is only 6TB. What in the world could be using that remaining space? I am at a loss, that's a _ton_ of space being used up. Is it some temporary=C2=A0allocation during script executi= on (seems ginormous, impossible)? It it some WAL log thing?

A fairly common cause of this is orphan replication slots so WAL files are retained. Check
to see if there is an inactive slot that may be preventing the files to be removed.



--
--

Lucio Chiessi<= /p>

Senior Database Administrator

Trustly,= Inc.

M: +55 2= 7 996360276

=C2=A0=C2=A0

=C2=A0=C2= =A0=C2=A0=C2= =A0<= /p>

<= /p>

= PayWithMyBank=C2=AE=C2=A0is= now part of=C2=A0Trustly


Please read our privacy policy here on how we process your person= al data in accordance with the Gen= eral Data Protection Regulation (EU) 2016/679 (the =E2=80=9C= GDPR=E2=80=9D) and other applicable data protection legislation

--
Born in Arizona, moved to Babylonia.
--------------k9nhfq83FiWWlqH85BuezPtc--