Re: Suggestion for Easier Cross-Database Query Handling in PostgreSQL

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Suggestion for Easier Cross-Database Query Handling in PostgreSQL
Date: 2026-05-15 23:22:58
Message-ID: 1439462.1778887378@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ron Johnson <ronljohnsonjr(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron Johnson 2026-05-15 23:57:45 Re: Suggestion for Easier Cross-Database Query Handling in PostgreSQL
Previous Message Ron Johnson 2026-05-15 22:56:46 Re: Suggestion for Easier Cross-Database Query Handling in PostgreSQL