Re: Avoid detoast overhead when possible

From: Nikita Malakhov <hukutoc(at)gmail(dot)com>
To: zhihuifan1213(at)163(dot)com
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Avoid detoast overhead when possible
Date: 2023-12-04 08:40:51
Message-ID: CAN-LCVMhwj6mGnjFg7hmNuTkwkyqHtiP8yVF_9DWuzXt2hT40Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi!

There's a view from the other angle - detoast just attributes that are
needed
(partial detoast), with optimized storage mechanics for JSONb. I'm preparing
a patch for it, so maybe the best results could be acquired by combining
these
two techniques.

What do you think?

--
Regards,
Nikita Malakhov
Postgres Professional
The Russian Postgres Company
https://postgrespro.ru/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2023-12-04 08:42:02 Re: A wrong comment about search_indexed_tlist_for_var
Previous Message John Naylor 2023-12-04 08:21:16 Re: [PoC] Improve dead tuple storage for lazy vacuum