I'm always interested in increasing evergreenness of old content, but I'm not sure how to do it yet.

What do you think about allowing reposting of old good posts, but at a considerable markup to make the repost?

Yet another approach I think that might be the goldilocks (no need for a compound primary key on "Item") is the history table pattern[^1]:

- create an "OldItem" table using [inheritance](https://www.postgresql.org/docs/current/ddl-inherit.html) with a foreign key reference to "Item".id
- on edits, copy the current "Item" to "OldItem" (taking care with primary keys and timestamps) and then edit the "Item" as usual

[^1]: https://www.reddit.com/r/PostgreSQL/comments/kt1agc/what_is_the_best_way_of_implementing/

k00b

Perpetual Edits?

siggy47

Yeah this could be difficult to scale. Depending on how it's implemented it might also require a compound primary key on items because their id alone would no longer identify them. 

I haven't looked into the diff approach much, but that'd be minimally invasive by comparison. I just don't have experience with it.

Footnotes