I presented a per-computed post_aggregates.inclusion column design as a temporary measure… I did all the leg work…
Aging out the data is essential. There seems to not be a realization that Lemmy works OK with 25,000 posts in it, but you have to tell PostgreSQL that you only really want what is fresh meat for end-users to read! published date is fundamental to the entire Lemmy experience, NEW posts start with 1 vote, and popularity starts with FRESH postings. Why do I have to keep saying this out loud when the PostgreSQL design of Lemmy ignores it!
I presented a per-computed post_aggregates.inclusion column design as a temporary measure… I did all the leg work…
Aging out the data is essential. There seems to not be a realization that Lemmy works OK with 25,000 posts in it, but you have to tell PostgreSQL that you only really want what is fresh meat for end-users to read! published date is fundamental to the entire Lemmy experience, NEW posts start with 1 vote, and popularity starts with FRESH postings. Why do I have to keep saying this out loud when the PostgreSQL design of Lemmy ignores it!