My PostgreSQL service is being turned off every day. I even recreated the service, but I’m still facing the same issue. Not sure what’s causing this.
Hi Irfan, could you please tell more about your service? what free tier is it? Are you having some activity after starting it?
I am on the Free Plan and running three services: MySQL, ValKey, and PostgreSQL. A few days ago, I started facing an issue where my PostgreSQL service is being powered off daily. Even when I turn it on and enable terminate protection, it still gets powered off.
I initially thought the issue might be due to the upgrade I did from PostgreSQL 16 to 17, so I deleted the service and recreated it using PostgreSQL 16. However, I’m still facing the same issue—every day I have to turn it back on, and it keeps getting powered off. All other services are working fine, so I’m not sure what’s causing this.
Thank you for bringing this to our attention, we are looking into it. While we do so, please tell us a little bit about how you use our services.
I’m happy to share that I use Aiven’s offerings for learning purposes. I follow exercises from various online courses and currently use three Aiven services — MySQL, PostgreSQL, and Valkey — to learn and sharpen my skills with some of the most popular databases and caching backends.
Thanks for your reply Irfan,
To provide an effective free tier, we implement an activity monitoring on our services. From our checks we noticed that the PostgreSQL database didn’t have any relevant activity. Therefore it’s automatically shut down after a period of time.
Is the inactivity period for the PostgreSQL service different from the other services? I have three services, but I’m only facing this issue with the PostgreSQL one.