Skip to content
This repository was archived by the owner on Mar 9, 2018. It is now read-only.

Best practise for maintaining rapns_notifications table. #203

Open

Description

@jimishjoban

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!

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions