public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: [email protected] <[email protected]>
Subject: Re: Suggestion for Easier Cross-Database Query Handling in PostgreSQL
Date: Fri, 15 May 2026 19:57:45 -0400
Message-ID: <CANzqJaDqtavaNgnwNHHqa-HJcMhBhhKDk75UxnuyPXp4gnHKdA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAHWFTRjCy3U30whQJBw8z5_8boq=V9MzbtHMh6HZVP3o-OaGxg@mail.gmail.com>
<[email protected]>
<CANzqJaBVAykTGq8j-gijJS-L0bK7duyO-k2xKgr8ZmO9mqxXMw@mail.gmail.com>
<[email protected]>
On Fri, May 15, 2026 at 7:22 PM Tom Lane <[email protected]> wrote:
> Ron Johnson <[email protected]> writes:
> > Why doesn't the shared OID space make cross-database queries possible?
>
> OIDs are not guaranteed unique across databases.
Ah.
> 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.
>
Even now, roles need privilege to access databases.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: Suggestion for Easier Cross-Database Query Handling in PostgreSQL
In-Reply-To: <CANzqJaDqtavaNgnwNHHqa-HJcMhBhhKDk75UxnuyPXp4gnHKdA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox