Skip to content

PostgreSQL database running on Amazon RDS that reached the maximum allowed storage size (16 TiB)

0

We have a PostgreSQL database running on Amazon RDS that reached the maximum allowed storage size (16 TiB). Because it ran out of space, the database is now stuck and won’t accept any connections to allow us to clean up or remove data. Since we can’t increase the storage further on regular RDS for PostgreSQL, what could be our best course of action?

It would seem that the limit is 65,536, according to https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_Storage.html.

But I'm not sure if the limit comes from the engine (Postgress 12.18) or the instance type db.m6g.4xlarge. Any guidance would be appreciated.

asked 2 years ago815 views

3 Answers
1

Hi,

This KC article explains you all the steps to get out of the status "ouf-of-space" for an DS instance: https://repost.aws/knowledge-center/rds-out-of-storage

Following its guidance should allow you get back to a working state and avoid to get it into it again.

Best,

Didier

EXPERT

answered 2 years ago

EXPERT

reviewed 2 years ago

0

I apologize, but there seems to be a misunderstanding in your question. The maximum storage size for PostgreSQL on Amazon RDS is actually 64 TiB, not 16 TiB as you mentioned. This limit applies to RDS for PostgreSQL, regardless of the specific engine version or instance type you're using.

Given this information, you should be able to increase your storage beyond 16 TiB, up to the 64 TiB limit. If you're unable to do so, it's possible there might be an issue with your specific configuration or a temporary service limitation.

However, if you're indeed at the maximum storage limit and unable to connect to your database, here are some potential courses of action:

  1. Contact AWS Support: If you're unable to increase storage or connect to your database, AWS Support can help diagnose and potentially resolve the issue.

  2. Take a snapshot and restore: You could take a snapshot of your current database and restore it to a new instance with more allocated storage. This would allow you to start with a clean slate and more room to grow.

  3. Consider Amazon Aurora PostgreSQL-Compatible Edition: Aurora PostgreSQL can automatically grow up to 128 TiB of storage, which might be beneficial if you anticipate needing more than 64 TiB in the future.

  4. Implement data archiving or partitioning strategies: To manage your data growth, consider implementing strategies to archive or partition your data. This can help you keep your active data set within manageable limits.

  5. Vertical scaling: If possible, consider upgrading to a larger instance type that might offer better performance and potentially allow for more efficient data management.

Remember, it's crucial to monitor your database storage usage and plan for growth before reaching critical limits. Regular maintenance, including data cleanup and optimization, can help prevent such situations in the future.
Sources
Cloud Relational Database – Amazon RDS Features – Amazon Web Services
Optimizing PostgreSQL Running on Amazon EC2 Using Amazon EBS - Optimizing PostgreSQL Running on Amazon EC2 Using Amazon EBS

answered 2 years ago

EXPERT

reviewed 2 years ago

0

Hello.

I think you can change the storage size to 64TB even on an existing database instance.
https://aws.amazon.com/about-aws/whats-new/2019/05/amazon-rds-mysql-mariadb-postgresql-64tib-support/?nc1=h_ls

You can change it by following the steps in the document below.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_PIOPS.ModifyingExisting.html

Since we can’t increase the storage further on regular RDS for PostgreSQL

By the way, where did you find out that you can't increase the storage size beyond 16TB?

EXPERT

answered 2 years ago

EXPERT

reviewed 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.