From: Tom Lane <tgl@sss.pgh.pa.us>
To: Greg Stark <stark@mit.edu>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: thierrym@gmail.com <thierrym@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #17902: export/import tenant not possible due to PG internal id on jsonB fields.
Date: Mon, 17 Apr 2023 12:18:37 -0400
Message-ID: <2444931.1681748317@sss.pgh.pa.us> (raw)
In-Reply-To: <CAM-w4HPP8Ki33mqkv10aYuMZMJwMuX4xyZ1_6r9yqg+iGLFFgQ@mail.gmail.com>
References: <17902-e75daa72de96a626@postgresql.org>
<CAKFQuwa4BsgppQ_w09nq1oXp=Hcvofo9k=tHjoTR+Po7KO2MUQ@mail.gmail.com>
<CAM-w4HPP8Ki33mqkv10aYuMZMJwMuX4xyZ1_6r9yqg+iGLFFgQ@mail.gmail.com>
Greg Stark <stark@mit.edu> writes:
> But large objects are kind of a leaky abstraction in that the internal
> ID becomes a user-visible identifier that is the only way users have
> of referencing these objects.
> I could see it being pretty useful to have an user-controlled
> identifier instead of forcing users to use OIDs.
You already can create LOBs with any identifier you want, as long
as it's an int4. The OP seems to think he can mix manual allocation
with automatic allocation of those IDs and it should just work.
> But the bad news is that I don't think anyone's really excited about
> working on the LOB facility.
Yeah. There's been some discussion of widening the identifiers to
int8, but I can't see going further than that. UUIDs would be a
disaster for a number of reasons, both performance and compatibility
related.
regards, tom lane
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: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, stark@mit.edu, david.g.johnston@gmail.com, thierrym@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17902: export/import tenant not possible due to PG internal id on jsonB fields.
In-Reply-To: <2444931.1681748317@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox