From: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
---|---|
To: | Jim Mlodgenski <jimmy76(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: RDS No free space |
Date: | 2023-05-21 17:47:54 |
Message-ID: | CAOC+FBW6yKx6Lcb-5MrjMNoU2LrQJGme57jNvMX7J+txx+Tb0Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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 <jimmy76(at)gmail(dot)com> wrote:
>
>
> On Sun, May 21, 2023 at 1:38 PM Wells Oliver <wells(dot)oliver(at)gmail(dot)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 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(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Lucio Chiessi | 2023-05-21 17:52:13 | Re: RDS No free space |
Previous Message | Jim Mlodgenski | 2023-05-21 17:42:49 | Re: RDS No free space |