Actually, if you look in pg_trigger, unnamed is technically the
constraint name and it should have a system generated constraint name
which you probably can use drop trigger on. It looks like part of
a FK constraint so I'm not sure how you got just 1/2 of it since
dropping subject should have
By comparing backups, I found
CREATE CONSTRAINT TRIGGER "unnamed" AFTER INSERT OR UPDATE ON "person" NOT
DEFERRABLE INITIALLY IMMEDIATE FOR EACH ROW EXECUTE PROCEDURE "RI_FKey_check_ins"
('unnamed', 'person', 'subject', 'UNSPECIFIED', 'subjectid', 'id');
Don't know where that came from, but
