#StackBounty: #postgresql #amazon-rds #postgresql-9.6 #aws #storage Postgres Database flagged as STORAGE FULL whereas there's 45 Gb…

Bounty: 50

I will start this post by stating that I am not very experienced in database administration, please accept my apologies for any unclear explanation you may find below.

We have a replica postgresql hosted on aws rds which stopped replicating last week. The instance was flagge as "Storage-full".

However, when looking at the free storage space on CloudWatch, we realized there were still roughly 46Gb available on the 50Gb-allocated instance. We increased the allocated space to 60Gb and everything went back to normal, but we knew the issue would come back and it did.

The main instance on which this one is replicated is autovacuumed. It is my understanding that any writes resulting on the main will be written on the replica, so this is probably not a vacuum issue.

Looking at cloudwatch metrics, there’s no indication of any problem that might cause this.

It appears logs could be the issue here but I don’t know where to look to investigate this option.

I will edit the question with any relevant information you might suggest in the comments.
Thanks for your help.

Get this bounty!!!

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.