Re: Should rolpassword be toastable? - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: Should rolpassword be toastable?
Date
Msg-id Zuwzp09o9uiG0f0F@nathan
Whole thread Raw
In response to Re: Should rolpassword be toastable?  (Alexander Lakhin <exclusion@gmail.com>)
Responses Re: Should rolpassword be toastable?
List pgsql-hackers
On Thu, Sep 19, 2024 at 06:00:00AM +0300, Alexander Lakhin wrote:
> 23.09.2023 21:00, Alexander Lakhin wrote:
>> 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.

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.

-- 
nathan



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pgsql: Don't enter parallel mode when holding interrupts.
Next
From: Tom Lane
Date:
Subject: Re: Should rolpassword be toastable?