Issues

• Require explicit opt-in when tracking an object that belongs to another extension

  Postgres-Extensions/object_reference#43 · Filter by author jnasbyupgrade opened on Aug 18, 2026

• Dedicated test coverage: streaming/physical replication (promotion, pg_upgrade-of-a-standby, permanently-empty _object_oid)

  Postgres-Extensions/object_reference#42 · Filter by author jnasbyupgrade opened on Aug 17, 2026

• Standard internal update-time disable mechanism, and refuse to self-track extension-owned objects

  Postgres-Extensions/object_reference#40 · Filter by author jnasbyupgrade opened on Aug 17, 2026

• Consider caching the OID sanity-check status within a transaction/backend

  Postgres-Extensions/object_reference#39 · Filter by author jnasbyupgrade opened on Aug 16, 2026

• Design: automated OID-repair for pg_dump/pg_upgrade — consolidated plan + review findings

  Postgres-Extensions/object_reference#38 · Filter by author jnasbyupgrade opened on Aug 16, 2026
  1

• Design: how (if at all) to auto-detect a binary pg_upgrade and trigger OID repair

  bug
  Postgres-Extensions/object_reference#25 · Filter by author jnasbyupgrade opened on Aug 5, 2026

• object_reference cannot survive binary pg_upgrade: _sentry_mv crashes it, and repair logic can't fix stale OIDs anyway

  bug
  Postgres-Extensions/object_reference#24 · Filter by author jnasbyupgrade opened on Aug 5, 2026
  1