Horton

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

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
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-16T01:24:32Z
Lists: pgsql-hackers 
On Tue, Oct 15, 2024 at 08:20:17PM -0500, Nathan Bossart wrote:
> On Wed, Oct 16, 2024 at 09:12:31AM +0900, Michael Paquier wrote:
> > -   if (!ctx->rel->rd_rel->reltoastrelid)
> > +   if (!OidIsValid(RelationGetToastRelid(ctx->rel)))
> > 
> > This set of diffs in 0002 is a nice cleanup.  I'd wish for relying
> > less on zero comparitons when assuming that InvalidOid is in use.
> 
> I'm wondering if there's any concern about this one causing back-patching
> pain.  If so, I can just add the macro for use in new code.

This bit does not concern me much.   manipulations of reltoastrelid
from Relations are not that common in bug fixes.

> I assume all of this will get compiled out in non-USE_ASSERT_CHECKING
> builds as-is, but I see no problem with surrounding it with an #ifdef to be
> sure.

Yeah, I'm not sure that that would always be the case when optimized.
Code generated can be dumb sometimes even if compilers got much
smarter in the last 10 years or so (not compiler guy here).
--
Michael

Commits

  1. Ensure we have a snapshot when updating various system catalogs.

  2. Remove pg_replication_origin's TOAST table.

  3. Restrict password hash length.

  4. Ensure we have a snapshot when updating pg_index entries.

  5. Add TOAST table to pg_index.

  6. Add toast tables to most system catalogs