Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem)
| От | Nikita Malakhov |
|---|---|
| Тема | Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) |
| Дата | |
| Msg-id | CAN-LCVNrY2CLdtkOzW=A3dhpAntVukdnEV4C+aZH5nPCyPNQUw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) ("Burd, Greg" <greg@burd.me>) |
| Ответы |
Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem)
Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) |
| Список | 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.
В списке pgsql-hackers по дате отправления: