Message-ID: <a9524f94-316c-349a-6e4d-79b878706f82@gmail.com>
Date: Thu, 19 Sep 2024 06:00:00 +0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.4.2
Subject: Re: Should rolpassword be toastable?
Content-Language: en-US
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>
References: <89e8649c-eb74-db25-7945-6d6b23992394@gmail.com>
 <1284094.1695479962@sss.pgh.pa.us>
 <67793ae1-3adc-a6e0-0bb3-c23a28c0627a@gmail.com>
In-Reply-To: <67793ae1-3adc-a6e0-0bb3-c23a28c0627a@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/a9524f94-316c-349a-6e4d-79b878706f82%40gmail.com>
Precedence: bulk

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