Re: Large expressions in indexes can't be stored (non-TOASTable)

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Nathan Bossart <nathandbossart@gmail.com>

Cc: Alexander Lakhin <exclusion@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, "Jonathan S. Katz" <jkatz@postgresql.org>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2024-10-30T23:45:15Z

Lists: pgsql-hackers

On Wed, Oct 30, 2024 at 03:54:32PM -0500, Nathan Bossart wrote:
> I'll manage.  0001 was a doozy to back-patch, and this obviously isn't a
> terribly pressing issue, so I plan to wait until after the November minor
> release to apply this.

Okay by me.

> I'm having second thoughts on 0002, so I'll
> probably leave that one uncommitted, but IMHO we definitely need 0003 to
> prevent this issue from reoccurring.

I liked your idea behind 0002, FWIW.  We do that for a lot of fields
already in a Relation.
--
Michael

Commits

Ensure we have a snapshot when updating various system catalogs.
- fe8ea7a2a893 17.6 landed
- ddfcfb7cec68 15.14 landed
- b7ba2c0308ce 13.22 landed
- b65be6ef00e2 14.19 landed
- 706054b11b95 18.0 landed
- 24135398f1e1 16.10 landed
Remove pg_replication_origin's TOAST table.
- 16bf24e0e471 18.0 landed
Restrict password hash length.
- 8275325a06ed 18.0 cited
Ensure we have a snapshot when updating pg_index entries.
- b52adbad4674 18.0 landed
Add TOAST table to pg_index.
- b52c4fc3c09e 18.0 landed
Add toast tables to most system catalogs
- 96cdeae07f93 12.0 cited