If my pg-fu is accurate, as the array grows, it would eventually get farmed out to a `pg_toast` table once the row no longer fits within a page (exact threshold

If my pg-fu is accurate, as the array grows, it would eventually get farmed out to a `pg_toast` table once the row no longer fits within a page (exact threshold might be lower). So it wouldn't be bloating any query path that doesn't use/depend on the array at the expense of forcing a toast lookup on every tuple that refers to the array. That should not be construed as an endorsement. I would think the array append might get expensive.