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: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>, Euler Taveira <euler(at)eulerto(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Alexander Lakhin <exclusion(at)gmail(dot)com>, "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: 2025-05-06 23:00:39
Message-ID: aBqUlxmOf9qvVIhT@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 06, 2025 at 11:41:49AM -0500, Nathan Bossart wrote:
> I brought this up with the RMT, and everyone seemed okay with committing it
> for v18.

Cool, thanks for the update.

> I can move it back to replorigin_create(). I don't have a strong opinion
> here.

I think that I would the check there, as that's safer in the long-run
to enforce the rule to all potential callers of this API. If the
votes balance in favor of keeping it in the SQL function, that's OK by
me as well, so feel free to ignore me if you feel strongly about it
overall.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-05-06 23:31:15 Re: queryId constant squashing does not support prepared statements
Previous Message Tatsuo Ishii 2025-05-06 22:28:02 Re: regdatabase