| From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Should rolpassword be toastable? |
| Date: | 2023-09-23 18:00:00 |
| Message-ID: | 67793ae1-3adc-a6e0-0bb3-c23a28c0627a@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
23.09.2023 17:39, Tom Lane wrote:
> I'm also now more than just slightly skeptical about whether
> pg_database should have a toast table. Has anybody tried,
> say, storing a daticurules field wide enough to end up
> out-of-line?
I tried, but failed, because pg_database accessed in InitPostgres() before
assigning MyDatabaseId only via the function GetDatabaseTupleByOid(),
which doesn't unpack the database tuple.
Another access to a system catalog with unassigned MyDatabaseId might occur
in the has_privs_of_role() call, but pg_auth_members contains no toastable
attributes.
So for now only pg_authid is worthy of condemnation, AFAICS.
Best regards,
Alexander
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2023-09-23 18:47:48 | Re: nbtree's ScalarArrayOp array mark/restore code appears to be buggy |
| Previous Message | Tom Lane | 2023-09-23 14:39:22 | Re: Should rolpassword be toastable? |