| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "thierrym(at)gmail(dot)com" <thierrym(at)gmail(dot)com>, "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:42:20 |
| Message-ID: | CAKFQuwa4BsgppQ_w09nq1oXp=Hcvofo9k=tHjoTR+Po7KO2MUQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | thierry melkebeke | 2023-04-17 14:57:32 | Re: BUG #17902: export/import tenant not possible due to PG internal id on jsonB fields. |
| Previous Message | Ann In Dark | 2023-04-17 14:04:04 | BUGREPORT: Performance degradation in Postgres with old_snapshot_threshold parameter in version 12.* |