You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After 1 year of activity, the table idempotency_key is full of rows, more than 400K taking 2 GB space on disk.
My question as in the title: Is it safe to delete rows of this table and what would be recommended to filter those keys that are safe to be deleted?
My first intention would be to just remove them based on the created_at criteria like more than a month in the past. But should I look also to the locked_at column?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
After 1 year of activity, the table idempotency_key is full of rows, more than 400K taking 2 GB space on disk.
My question as in the title: Is it safe to delete rows of this table and what would be recommended to filter those keys that are safe to be deleted?
My first intention would be to just remove them based on the created_at criteria like more than a month in the past. But should I look also to the locked_at column?
Beta Was this translation helpful? Give feedback.
All reactions