Thank you Adam and Christoph,
You are totally right, that AWS support is the one to help me with this problem.
I am in contact with them for quite some time on this problem and as there was no progress on resolving this,
I tried to find some insight or trick that I missed here. It's a long shot (:
Best Regards
Chris
On Fri, Aug 7, 2020 at 4:22 PM Christoph Moench-Tegeder <cmt@xxxxxxxxxxxxxx> wrote:
## Chris Borckholder (chris.borckholder@xxxxxxxxxxxx):
> We are experiencing a strange situation with an AWS Aurora postgres
> instance.
The main problem here is that "Amazon Aurora" is not PostgreSQL.
If I understand Amazon's documentation, what you are using is
officially named "Amazon Aurora with PostgreSQL Compatibility",
and that sums is up quite nicely: Aurora is a database engine
developed at Amazon - and it's inner workings are not publically
documented.
Whatever is using up that disk space - only AWS Support can know.
Regards,
Christoph
--
Spare Space
