>> If the application's behavior is simple and well-defined, this might >> be good enough, of course. > > > FWIW when I read the original email in the thread I got the impression that > the application behavior was pretty simple WRT this table. But of course I > could easily be wrong...
You are not wrong. The use case is in fact the `userpref` table used by Spamassassin. Left unmaintained, and given a large-enough user base, this has the tendency to grow considerably over time, so we want to gradually remove entries not actually used any more. (And we don’t want to patch Spamassassin core code to do this by itself…) I’ll give it a try with ab/using RLS, which we use for some other use cases anyway already. Thanks a lot for the suggestions in the thread, much appreciated! — Matthias
