Re: Should rolpassword be toastable?
Nathan Bossart <nathandbossart@gmail.com>
From: Nathan Bossart <nathandbossart@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alexander Lakhin <exclusion@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-09-19T17:44:32Z
Lists: pgsql-hackers
On Thu, Sep 19, 2024 at 10:31:15AM -0400, Tom Lane wrote: > Nathan Bossart <nathandbossart@gmail.com> writes: >> Hm. It does seem like there's little point in giving pg_authid a TOAST >> table, as rolpassword is the only varlena column, and it obviously has >> problems. But wouldn't removing it just trade one unhelpful internal error >> when trying to log in for another when trying to add a really long password >> hash (which hopefully nobody is really trying to do in practice)? I wonder >> if we could make this a little more user-friendly. > > We could put an arbitrary limit (say, half of BLCKSZ) on the length of > passwords. Something like that could be good enough. I was thinking about actually validating that the hash had the correct form, but that might be a little more complex than is warranted here. -- nathan
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