On Dec 31, 2024, at 9:20 AM, Tomas Vondra <tomas@vondra.me> wrote:
Speaking of retention, it would be nice if this feature allowed users to
DELETE from the view that presented the data. That would allow for any
kind of custom config that someone could dream up.
I really don't intend / want to do that. That significantly increasesthe complexity, turning an append-only file into something that'sessentially almost a regular table. Yes, even with the append-only filethere's need to be a way to deal with dropped objects, but supportingarbitrary deletes seems much more demanding.There should be a way to reset the stats, of course. But only a fairlycoarse one.
My thought was that you’d just accumulate the pkey of everything being deleted until end of transaction and then use that to rewrite the table. On the surface that doesn’t seem too terrible, especially depending on how dropped objects as well as aging out old data is handled.
Either way I just wanted to put the idea out there as something I think would be useful, especially since it might influence parts of the simple design. I certainly agree it’s not a mandatory feature.
