This repository has been archived by the owner on Mar 9, 2018. It is now read-only.

Best practise for maintaining rapns_notifications table. #203

Open

jimishjoban opened this issue Feb 28, 2015 · 0 comments

jimishjoban commented Feb 28, 2015

Hello,

Is there a way to auto-erase (configurable) successful notification sent... So rapns_notifications table does not grow in size...

I just realised that my rapns_notifications table had grown to 22030769 rows and hence becoming increasingly slow...

Do you suggest to write a background job to clean up successful notifications or is there a better way to manage?

Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.