| From: | Jim Mlodgenski <jimmy76(at)gmail(dot)com> |
|---|---|
| To: | Wells Oliver <wells(dot)oliver(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:42:49 |
| Message-ID: | CAB_5SRfhyHDXQppTv2HUvj7oTHgf=BLJrTjMFj-W4LWorX-YhQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wells Oliver | 2023-05-21 17:47:54 | Re: RDS No free space |
| Previous Message | Wells Oliver | 2023-05-21 17:37:40 | Re: RDS No free space |