| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| 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-27 20:02:52 |
| Message-ID: | aDYabIxCPxu4GZxT@nathan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 08, 2025 at 08:55:08AM +0900, Michael Paquier wrote:
> On Wed, May 07, 2025 at 02:55:49PM -0500, Nathan Bossart wrote:
>> Committed with that change. That takes care of a good chunk of these TOAST
>> snapshot problems. I think there are about 4 others left, unless something
>> has changed since I last checked. I hope to look into those again soon.
>
> Thanks, for both things.
Here is what I have staged for commit for the others. I'm hoping to push
these in the next couple of days.
--
nathan
| Attachment | Content-Type | Size |
|---|---|---|
| v6-0001-Ensure-we-have-a-snapshot-when-updating-va.patch.master | text/plain | 8.3 KB |
| v6-0001-Ensure-we-have-a-snapshot-when-updating-vario.patch.v13 | text/plain | 3.6 KB |
| v6-0001-Ensure-we-have-a-snapshot-when-updating-vario.patch.v14 | text/plain | 4.4 KB |
| v6-0001-Ensure-we-have-a-snapshot-when-updating-vario.patch.v15 | text/plain | 9.3 KB |
| v6-0001-Ensure-we-have-a-snapshot-when-updating-vario.patch.v16 | text/plain | 9.4 KB |
| v6-0001-Ensure-we-have-a-snapshot-when-updating-vario.patch.v17 | text/plain | 9.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matheus Alcantara | 2025-05-27 20:45:17 | Re: Fixing memory leaks in postgres_fdw |
| Previous Message | Robert Haas | 2025-05-27 19:51:40 | Re: Tightening DecodeNumberField's parsing rules |