| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, 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: | 2025-04-04 14:28:27 |
| Message-ID: | Z-_sixINC08J_SQB@nathan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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...
[0] https://postgr.es/m/ZvOMBhlb5zrBCG5p%40paquier.xyz
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2025-04-04 14:30:46 | Re: [PoC] Reducing planning time when tables have many partitions |
| Previous Message | David Rowley | 2025-04-04 14:22:57 | Re: [PoC] Reducing planning time when tables have many partitions |