Re: BUG #17902: export/import tenant not possible due to PG internal id on jsonB fields.

From: thierry melkebeke <thierrym(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17902: export/import tenant not possible due to PG internal id on jsonB fields.
Date: 2023-04-17 14:57:32
Message-ID: CAOhA-dSkZ=V8Lh418a25VGwfO1FLUmar1Dd+z+My_=xVLA30CQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

hi

thanks for the quick answer
I understand this is not considered as a bug, this is more a not covered
use case.
then it means it's not working: do not use large objects with multi
tenant db
or do it, but do not expect to be able to export/import one specific tenant

Le lun. 17 avr. 2023 à 16:42, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
a écrit :

> On Monday, April 17, 2023, PG Bug reporting form <noreply(at)postgresql(dot)org>
> wrote:
>
>> The following bug has been logged on the website:
>>
>> Bug reference: 17902
>> Logged by: thierry melkebeke
>> Email address: thierrym(at)gmail(dot)com
>> PostgreSQL version: 14.6
>> Operating system: no matter
>> Description:
>>
>> To solved this, I think the internal tables to store large objects should
>> use uuid instead of classical sequences]
>>
>
> This isn’t a bug and changing OIDs from integers to UUIDs isn’t going to
> happen.
>
> David J.
>

--
Thierry Melkebeke

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Greg Stark 2023-04-17 15:51:49 Re: BUG #17902: export/import tenant not possible due to PG internal id on jsonB fields.
Previous Message David G. Johnston 2023-04-17 14:42:20 Re: BUG #17902: export/import tenant not possible due to PG internal id on jsonB fields.