Postgres Pro
Downloads
Home   >   mailing lists

Re: Avoid detoast overhead when possible - Mailing list pgsql-hackers

From Nikita Malakhov
Subject Re: Avoid detoast overhead when possible
Date
Msg-id CAN-LCVMhwj6mGnjFg7hmNuTkwkyqHtiP8yVF_9DWuzXt2hT40Q@mail.gmail.com
Whole thread Raw
In response to Avoid detoast overhead when possible  (zhihuifan1213@163.com)
Responses Re: Avoid detoast overhead when possible
List pgsql-hackers
Tree view
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

pgsql-hackers by date:

Previous
From: John Naylor
Date:
Subject: Re: [PoC] Improve dead tuple storage for lazy vacuum
Next
From: Richard Guo
Date:
Subject: Re: A wrong comment about search_indexed_tlist_for_var