Postgres Pro
Downloads
Home   >   mailing lists

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

From thierry melkebeke
Subject Re: BUG #17902: export/import tenant not possible due to PG internal id on jsonB fields.
Date
Msg-id CAOhA-dSkZ=V8Lh418a25VGwfO1FLUmar1Dd+z+My_=xVLA30CQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17902: export/import tenant not possible due to PG internal id on jsonB fields.  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-bugs
Tree view
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.g.johnston@gmail.com> a écrit :
On Monday, April 17, 2023, PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      17902
Logged by:          thierry melkebeke
Email address:      thierrym@gmail.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

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #17902: export/import tenant not possible due to PG internal id on jsonB fields.
Next
From: Greg Stark
Date:
Subject: Re: BUG #17902: export/import tenant not possible due to PG internal id on jsonB fields.