| From: | Nikita Malakhov <hukutoc(at)gmail(dot)com> |
|---|---|
| To: | "Burd, Greg" <greg(at)burd(dot)me> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Hannu Krosing <hannuk(at)google(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) |
| Date: | 2025-07-08 18:31:29 |
| Message-ID: | CAN-LCVNrY2CLdtkOzW=A3dhpAntVukdnEV4C+aZH5nPCyPNQUw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi!
Greg, thanks for the interest in our work!
Michael, one more thing forgot to mention yesterday -
#define TOAST_EXTERNAL_INFO_SIZE (VARTAG_ONDISK_OID + 1)
static const toast_external_info
toast_external_infos[TOAST_EXTERNAL_INFO_SIZE]
VARTAG_ONDISK_OID historically has a value of 18
and here we got an array of 19 members with only 2 valid ones.
What do you think about having an individual
TOAST value id counter per relation instead of using
a common one? I think this is a very promising approach,
but a decision must be made where it should be stored.
--
Regards,
Nikita Malakhov
Postgres Professional
The Russian Postgres Company
https://postgrespro.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | sunil s | 2025-07-08 18:31:55 | Re: Unnecessary delay in streaming replication due to replay lag |
| Previous Message | Andrey Borodin | 2025-07-08 18:25:44 | Re: What is a typical precision of gettimeofday()? |