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

From Amit Kapila
Subject Re: Large expressions in indexes can't be stored (non-TOASTable)
Date
Msg-id CAA4eK1LeMM8royHj5UyMBDbspD7+_70AJkV4Uji122hmkn7jOw@mail.gmail.com
Whole thread Raw
In response to Re: Large expressions in indexes can't be stored (non-TOASTable)  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: Large expressions in indexes can't be stored (non-TOASTable)
List pgsql-hackers
On Fri, Apr 4, 2025 at 7:58 PM Nathan Bossart <nathandbossart@gmail.com> wrote:
>
> On Fri, Apr 04, 2025 at 05:16:43PM +0530, Amit Kapila wrote:
> > Can we dodge adding this push call if we restrict the length of the
> > origin name to some reasonable limit like 256 or 512 and avoid the
> > need of toast altogether?
>
> We did consider just removing pg_replication_origin's TOAST table earlier
> [0], but we decided against it at that time.  Maybe it's worth
> reconsidering...
>

I don't see any good reason in that email for not removing the TOAST
table for pg_replication_origin. I would prefer to remove it rather
than add protection related to its access.

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: jian he
Date:
Subject: Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row
Next
From: Andrei Lepikhov
Date:
Subject: Re: Some problems regarding the self-join elimination code