nostr:npub1q3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnws6cd26p nostr_tags started growing quite quickly, currently taking up 2.4x more space than the events themselves, with the three created_at index variations taking up 3/4's of that
a task to clear martian (non local/follow) events/tags created later than N days would be appreciated
at least adding three minor indexes as suggested by https://github.com/ankane/dexter seems to have lessened the read stampede
CREATE INDEX CONCURRENTLY ON "public"."nostr_events" ("created_at");
CREATE INDEX CONCURRENTLY ON "public"."nostr_events" ("pubkey", "created_at");
CREATE INDEX CONCURRENTLY ON "public"."nostr_tags" ("event_id");
although public.nostr_events (kind, content) isn't possible to add because that has txt longer than the 8191 size limit
