Re: Suggestion for Easier Cross-Database Query Handling in PostgreSQL
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
Date: 2026-05-15T23:22:58Z
Lists: pgsql-general
Ron Johnson <ronljohnsonjr@gmail.com> writes: > Why doesn't the shared OID space make cross-database queries possible? OIDs are not guaranteed unique across databases. To make this work transparently, we'd have to change all internal APIs to use database OID + object OID, not just object OID, as object identifiers. That would be horrendously invasive, not to mention probably costly in performance (by doubling the width of cache keys, for instance). But totally independently of implementation considerations, it's not apparent to me that this would be a good idea. As Frank mentioned, Postgres has always treated databases as isolation boundaries. Changing that would probably break a lot of peoples' installation designs. regards, tom lane