Re: Should rolpassword be toastable?
Alexander Law <exclusion@gmail.com>
From: Alexander Lakhin <exclusion@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>, Nathan Bossart <nathandbossart@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-09-19T03:00:00Z
Lists: pgsql-hackers
Hello Tom and Nathan, 23.09.2023 21:00, Alexander Lakhin wrote: > 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? > > So for now only pg_authid is worthy of condemnation, AFAICS. > Let me remind you of this issue in light of b52c4fc3c. Yes, it's opposite, but maybe it makes sense to fix it now in the hope that ~1 year of testing will bring something helpful for both changes. Best regards, Alexander
Commits
-
Restrict password hash length.
- 8275325a06ed 18.0 landed
-
Remove pg_authid's TOAST table.
- 6aa44060a3c9 18.0 landed
-
Remove arbitrary restrictions on password length.
- 67a472d71c98 14.0 cited