Re: Unexplained disk usage in AWS Aurora Postgres

From: Mohamed Wael Khobalatte <mkhobalatte(at)grubhub(dot)com>
To: Chris Borckholder <chris(dot)borckholder(at)bitpanda(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Unexplained disk usage in AWS Aurora Postgres
Date: 2020-08-06 01:18:10
Message-ID: CABZeWdxCOkmQhgscxpxBJcT_mfaOWFMy=wjwcz+mFr_fHEb08g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Aug 4, 2020 at 4:39 AM Chris Borckholder <
chris(dot)borckholder(at)bitpanda(dot)com> wrote:

> Hi!
>
> We are experiencing a strange situation with an AWS Aurora postgres
> instance.
> The database steadily grows in size, which is expected and normal.
> After enabling logical replication, the disk usage reported by AWS metrics
> increases much faster then the database size (as seen by \l+ in psql). The
> current state is that database size is ~290GB, while AWS reports >640GB
> disk usage.
> We reached out to AWS support of course, which is ultimately responsible.
> Unfortunately they were not able to diagnose this until now.
>
> I checked with the queries from wiki
> https://wiki.postgresql.org/wiki/Disk_Usage , which essentially give the
> same result.
> I tried to check on wal segment file size, but we have no permission to
> execute select pg_ls_waldir().
> The replication slot is active and it also progresses
> (pg_replication_slots.confirmed_flush_lsn increases and is close to
> pg_current_wal_flush_lsn).
>
> Can you imagine other things that I could check from within postgres with
> limited permissions to diagnose this?
>
> Best Regards
> Chris
>
>
If you do archive wal files, maybe the archive_command is failing?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rama Krishnan 2020-08-06 02:10:01 Doubt in pgbase
Previous Message David Gauthier 2020-08-05 21:36:54 Postgres, High Availability, patching servers sequentially