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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Large expressions in indexes can't be stored (non-TOASTable)
Date: 2024-10-30 23:45:15
Message-ID: ZyLFC24UpcIJJmwT@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2024-10-30 23:47:04 Re: Add isolation test template in injection_points for wait/wakeup/detach
Previous Message Peter Smith 2024-10-30 23:11:46 Re: Pgoutput not capturing the generated columns