Skip to main content
Notice removed Draw attention by CommunityBot
Bounty Ended with no winning answer by CommunityBot

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 rdsAWS RDS, which stopped replicating last week. The instance was flaggeflagged as "Storage-full"Storage-full.

However, whenwhile looking at the free storage space on CloudWatchCloudWatch, 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 autovacuumedauto vacuumed. It is my understanding that anyI think 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 noI could not find any indication of any problem that might cause thisin CloudWatch metrics.

It appears that the 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.

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.

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 flagged as Storage-full.

However, while 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 auto vacuumed. I think any writes resulting on the main will be written on the replica, so this is probably not a vacuum issue.

I could not find any indication of problem in CloudWatch metrics.

It appears that the 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.

Notice added Draw attention by Vincent Rolea
Bounty Started worth 50 reputation by Vincent Rolea
Source Link

Postgres Database flagged as STORAGE FULL whereas there's 45 Gb available

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.